Glauber de Oliveira Costa wrote:
> The interrupt initialization routine becomes native_init_IRQ and will
> be overriden later in case paravirt is on.
>
> The interrupt vector is made global, so paravirt guests can reference
> it in their initializations.
Why? And if so, wouldn't it be better to
On Wed, 08 Aug 2007 22:08:38 -0700 (PDT)
David Miller <[EMAIL PROTECTED]> wrote:
> If this patch works I am very happy with it, since lazy_mmu_prot_update()
> is now completely gone as a result.
>
> Acked-by: David S. Miller <[EMAIL PROTECTED]>
>
Of course, this patch fixes SIGILL/nfs on
Andi Kleen wrote:
>> @@ -264,13 +270,64 @@ struct thread_struct {
>> set_fs(USER_DS);
>> \
>> } while(0)
>>
>> -#define get_debugreg(var, register) \
>> -__asm__("movq %%db" #register ", %0"
On 8/8/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> >
> > @@ -264,13 +270,64 @@ struct thread_struct {
> > set_fs(USER_DS);
> >\
> > } while(0)
> >
> > -#define get_debugreg(var, register) \
> > -
On Mon, Jul 30, 2007 at 06:13:42PM +0200, Jan Blunck wrote:
> On union-mounted file systems the lookup function must also visit lower layers
> of the union-stack when doing a lookup. This patches add support for
> union-mounts to cached lookups and real lookups.
>
> We have 3 different styles of
Hi Steven,
On Thu, 09 Aug 2007 00:36:31 -0400 Steven Rostedt <[EMAIL PROTECTED]>
wrote:
>
> Well, some may be merged with x86_64 later, but for now we move them
> out of the way. Later on we can start seeing how we can combine
> some of these files to be arch generic.
>
> Signed-off-by: Steven
Rusty Russell wrote:
> On Thu, 2007-08-09 at 02:24 +0200, Andi Kleen wrote:
>
>> Not sure what's best. Ok using a normal export is easiest and not
>> that big an issue.
>>
>
> Yeah, there's also been talk of breaking up paravirt_ops into multiple
> structs by area, which would lead
I saw we call IS_ERR(ptr) after executing kthread_run() each time.
But we don't need to call IS_ERR(ptr) after kmalloc().
My understanding is,
the kernel pointer ptr for IS_ERR to check should be page aligned, so
its kernel address should be less than 0xf000(or 0x
f000, 64bits),
Glauber de Oliveira Costa wrote:
> On 8/8/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:
>
>> Glauber de Oliveira Costa wrote:
>>
>>> Hi folks,
>>>
>>> After some time away from it, and a big rebase as a consequence, here
>>>
>> is
>>
>>> the updated version of paravirt_ops for
Hi Steven,
I am just being pedantic here (and I should have beaten up on Rusty
before now ... :-)
On Thu, 09 Aug 2007 00:36:30 -0400 Steven Rostedt <[EMAIL PROTECTED]>
wrote:
>
> --- a/include/asm-i386/lg.h
> +++ b/include/asm-i386/lg.h
> @@ -1,5 +1,5 @@
> -#ifndef _LGUEST_H
> -#define
On Tue, Aug 07, 2007 at 11:37:06PM +0200, Jan Engelhardt wrote:
>
> On Aug 7 2007 13:43, Greg KH wrote:
> >
> >added this 64-bit bug:
> >
> >
> > unsigned int flags;
> >
> > spin_lock_irqsave(>lock, flags);
> >
> >
> >irq 'flags' must be unsigned long, not unsigned
On Wed, Aug 08, 2007 at 10:09:18PM -0700, Andrew Morton wrote:
> Often such an early crash is due to a config problem. eg: chose the
> wrong CPU type. So I'd recommend that you triple-check that config,
> especially under "Processor type and features" before diving into into the
> bisection
Steven Rostedt wrote:
> /*
>* x86 arch doesn't have an easy way to find out where
>* gs is located. So we need to read the MSR. But first
>* we need to save off the rcx, rax and rdx.
>
Why don't you store it in gs? movq %gs:my_gs_base, %rax?
J
-
To
On Sat, 4 Aug 2007, Ray Lee wrote:
On 8/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Sat, 4 Aug 2007, Ingo Molnar wrote:
At least on a surface level, your report has some similarities to
http://lkml.org/lkml/2007/5/21/84 . In that message, John Miller
mentions several things he
On Thu, 9 Aug 2007 07:57:43 +0300 Mikko Rapeli <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 08, 2007 at 05:02:11PM -0700, Andrew Morton wrote:
> > On Thu, 9 Aug 2007 01:31:20 +0300
> > Mikko Rapeli <[EMAIL PROTECTED]> wrote:
> >
> > > Since 2.6.23-rc1 I can't boot an old k6 (with a funky IDE drive
sched_rt.c : requeue_task_rt()
The comment states the problem requeue no dequeue.
Put task to the end of the run list without the overhead of dequeue
followed by enqueue.
dequeue_task_rt() updates stats. Where without calling
it will skip the stat update.
Thus, shouldn't requeue_task_rt() call
gcc-4.2 is a lot more picky about its symbol handling. EXPORT_SYMBOL
no longer works on symbols that are undefined or defined with static scope.
For example, with CONFIG_PROFILE off, I see:
kernel/profile.c:206: error: __ksymtab_profile_event_unregister causes a
section type conflict
From: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
Date: Thu, 9 Aug 2007 13:57:21 +0900
> Changelog v8 -> v9.
> - removed sync_icache_dcache().
> - modified set_pte() rather than adding new complexed macro.
>
> Old stories
> - For synching icache and dcache before set_pte(), I added a new macro for
On Wed, 8 Aug 2007 21:18:25 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 8 Aug 2007, Chris Snook wrote:
> >
> > Some architectures currently do not declare the contents of an atomic_t to
> > be
> > volatile. This causes confusion since atomic_read() might not actually
flush icache before set_pte() for ia64 take 9.
The whole code was changed. This is a new trial.
Changelog v8 -> v9.
- removed sync_icache_dcache().
- modified set_pte() rather than adding new complexed macro.
Old stories
- For synching icache and dcache before set_pte(), I added a new macro
On Wed, Aug 08, 2007 at 05:02:11PM -0700, Andrew Morton wrote:
> On Thu, 9 Aug 2007 01:31:20 +0300
> Mikko Rapeli <[EMAIL PROTECTED]> wrote:
>
> > Since 2.6.23-rc1 I can't boot an old k6 (with a funky IDE drive worth
> > testing
> > with libata). The boot hangs without a sound or letter prints
In migration, a new page should be cache flushed before set_pte()
in some archs which have virtually-tagged cache..
I'll separate this from patch set in the next time.
Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
---
mm/migrate.c |1 +
1 file changed, 1 insertion(+)
Index:
synching Icache and Dcache before set_pte() for ia64 take9.
take8 got negative review as "ia64 specific codes are scattered over vm layer
and it will not be able to be maintained." And adivce from David Miller
(thanks!)
was modifiying set_pte().
This version modifies set_pte() for inserting
The lg.h file has lots of i386 specific information. Move it over to the asm
directory where it belongs.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/i386/kernel/asm-offsets.c|2 +-
drivers/lguest/core.c |2 +-
drivers/lguest/hypercalls.c |
Have the lguest launcher include e820.h via asm/e820.h instead of explicitly
saying i386.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
Documentation/lguest/lguest.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/lguest/lguest.c
Add a generic lg.h that can be included from lguest files.
This file will hold the data that can be shared across archs.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/i386/kernel/asm-offsets.c|2 +-
drivers/lguest/core.c |2 +-
The hvc_lguest uses __pa in the const initialization.
In some architectures, __pa() is not constant so this fails in compiles.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/char/hvc_lguest.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git
[
Changes since last version.
- Move lg.h to include/asm instead (suggested by Rusty Russel)
- All steps of the series compiles (suggested by Stephen Rothwell)
- Better ifdef header naming (suggested by Stephen Rothwell)
- Added Andi Kleen to CC (forgot to on V1)
]
Hi all,
I've been
1) * Possible wasted stats overhead during dequeue..
sched_rt.c:
Is RT check needed within a RT func?
dequeue_task_rt() calls update_curr_rt()
which checks for priority of RR or FIFO.
WITHIN..
static inline void update_curr_rt(struct rq *rq)
are the two lines..
if (!task_has_rt_policy(curr))
On Thu, 9 Aug 2007, Andi Kleen wrote:
> On Wednesday 08 August 2007 23:01, Christoph Lameter wrote:
> > From: Mike Travis <[EMAIL PROTECTED]>
>
> Why does Mike not submit his patches by himself?
Its his first patch and I wanted to help out a bit He will submit
them himself in the future.
On Wed, 8 Aug 2007, Chris Snook wrote:
>
> Some architectures currently do not declare the contents of an atomic_t to be
> volatile. This causes confusion since atomic_read() might not actually read
> anything if an optimizing compiler re-uses a value stored in a register, which
> can break
Hi Joerg:
* Joerg Sommrey <[EMAIL PROTECTED]> [2007-08-08 17:17:16 +0200]:
> Hi Mark,
>
> just to eliminate as many impacts as possible, I did:
> - reinstall the unmodified sensors.conf from Tyan's support page
> - power off before rebooting
>
> A call to "sensors -s" is done without errors in
On Wed, Aug 08, 2007 at 06:48:24PM -0700, David Miller wrote:
> From: Herbert Xu <[EMAIL PROTECTED]>
> Date: Thu, 09 Aug 2007 09:03:27 +0800
>
> > Such loops should always use something like cpu_relax() which comes
> > with a barrier.
>
> This is an excellent point.
>
> And it needs to be
In setup_APIC_timer with the HPET in use, a condition can arise while
waiting for the next irq slice to expire on the HPET which will either
cause an NMI watchdog to fire or a 3 minute busy loop if the NMI
watchdog is disabled.
The HPET comparator and the counter keep incrementing during its
Hello,
I would like to know who the USB system works under linux, I mean,
I would like to write a kernel module who will create a virtual USB
device, so that the kernel will think that a hardware USB device is
exists, were can I start?
Thanks.
-
To unsubscribe from this list: send the line
Hi:
Whenever 8139too is loaded via modprobe, the entire system hangs.
If we compile the kernel with CONFIG_8139TOO_PIO=y, the problem
goes away. However, since every distro we've tried does not
compile the module this way, all of the installation CDs hang.
We were able to find a specially
* Joe Perches <[EMAIL PROTECTED]> [2007-08-07 18:09:39 -0700]:
> Found these while looking at printk uses.
>
> Add missing newlines to dev_ uses
> Add missing KERN_ prefixes to multiline dev_s
> Fixed a wierd->weird spelling typo
> Added a newline to a printk
>
> Signed-off-by: Joe Perches
On Thu, Aug 09, 2007 at 04:39:20AM +0200, J??rn Engel wrote:
> Fair enough. Does the file still make sense in include/linux/ then?
I don't think so. Except for the one filesystem that's out there to repeat
past mistakes all recent ones keep their headers in their impleementation
directories.
-
On Thu, 9 August 2007 03:39:06 +0100, Christoph Hellwig wrote:
> On Thu, Aug 09, 2007 at 04:32:17AM +0200, J??rn Engel wrote:
> > On Thu, 9 August 2007 01:19:13 +0100, Christoph Hellwig wrote:
> > > On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> > > > ---
Ross Fawcett wrote:
What would you define a media error as though? I mean my first thought
is a bad block, but a scan of the disc doesn't report anything like
that. It also seems to be intermittent, however recently it has been
reproducible.
It's not mine to define. It's precisely what your
On Thu, Aug 09, 2007 at 04:32:17AM +0200, J??rn Engel wrote:
> On Thu, 9 August 2007 01:19:13 +0100, Christoph Hellwig wrote:
> > On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> > > --- linux-2.6.21logfs/include/linux/Kbuild~logfs 2007-08-08
> > > 02:57:37.0 +0200
> > >
On Thu, 9 August 2007 01:19:13 +0100, Christoph Hellwig wrote:
> On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> > --- linux-2.6.21logfs/include/linux/Kbuild~logfs2007-08-08
> > 02:57:37.0 +0200
> > +++ linux-2.6.21logfs/include/linux/Kbuild 2007-08-08
What would you define a media error as though? I mean my first thought
is a bad block, but a scan of the disc doesn't report anything like
that. It also seems to be intermittent, however recently it has been
reproducible.
- Ross
Jeff Garzik wrote:
> Ross Fawcett wrote:
>> The errors I get are
Hi everyone,
I find a function(clockevents_unregister_notifier) which is not
called by anything in tree.
Signed-off-by: Miao Xie <[EMAIL PROTECTED]>
diff -urN linux-2.6.23-rc2.orig/kernel/time/clockevents.c
linux-2.6.23-rc2/kernel/time/clockevents.c
---
Ross Fawcett wrote:
The errors I get are like these.
[ 1073.018375] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 1073.018382] ata4.00: (irq_stat 0x00020002, device error via SDB FIS)
[ 1073.018389] ata4.00: cmd 60/80:00:80:6f:b6/00:00:04:00:00/40 tag 0
cdb 0x0 data 65536 in
[
--
On Thu, 9 Aug 2007, Stephen Rothwell wrote:
> On Wed, 08 Aug 2007 20:32:15 -0400 Steven Rostedt <[EMAIL PROTECTED]>
> wrote:
> >
> > diff --git a/drivers/lguest/i386/lg.h b/drivers/lguest/i386/lg.h
> > index 64f0abe..c5ea14c 100644
> > --- a/drivers/lguest/i386/lg.h
> > +++
I think that I may have spotted a minor bug in the 2.6.23 kernel and its
relationship with the EXT3 file system. I apologize in advance if I am
mistaken, reporting a problem that is already known (I did not spot it
in Bugzilla) or if I am reporting it to the wrong forum. I made the
decision a
--
On Thu, 9 Aug 2007, Stephen Rothwell wrote:
> On Wed, 08 Aug 2007 20:32:13 -0400 Steven Rostedt <[EMAIL PROTECTED]>
> wrote:
> >
> > Add a generic lg.h file to call the architecture specific one.
>
> Please combine this with the previous patch so that the tree will build
> at each step.
Yeah,
Hi all,
I'm trying to track down whats causing the problems with a Silicon Image
3124 PCI/PCI-X sata card and running it under linux.
A quick rundown on the hardware that is in use.
Athlon X2 4200+
Asus A8S-X Mobo
Silicon Image 3124 4port SATA RAID card (using a PCI slot)
5x500gb WDJB 500gb
On Wed, 08 Aug 2007 20:32:15 -0400 Steven Rostedt <[EMAIL PROTECTED]>
wrote:
>
> diff --git a/drivers/lguest/i386/lg.h b/drivers/lguest/i386/lg.h
> index 64f0abe..c5ea14c 100644
> --- a/drivers/lguest/i386/lg.h
> +++ b/drivers/lguest/i386/lg.h
> @@ -20,6 +20,8 @@
> #include
> #include
>
From: Herbert Xu <[EMAIL PROTECTED]>
Date: Thu, 09 Aug 2007 09:03:27 +0800
> Such loops should always use something like cpu_relax() which comes
> with a barrier.
This is an excellent point.
And it needs to be weighed with the error prone'ness Andrew mentioned.
There probably is a middle ground
On Wed, 08 Aug 2007 20:32:13 -0400 Steven Rostedt <[EMAIL PROTECTED]>
wrote:
>
> Add a generic lg.h file to call the architecture specific one.
Please combine this with the previous patch so that the tree will build
at each step.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
On Wed, Aug 08, 2007 at 12:26:55PM +0200, Andi Kleen wrote:
>
> > *
> > * (the type definitions are in asm/spinlock_types.h)
> > */
> >
> > +#if (NR_CPUS > 256)
> > +#error spinlock supports a maximum of 256 CPUs
> > +#endif
> > +
> > static inline int __raw_spin_is_locked(raw_spinlock_t
On Wed, Aug 08, 2007 at 01:31:58PM -0400, [EMAIL PROTECTED] wrote:
> On Wed, 08 Aug 2007 06:24:44 +0200, Nick Piggin said:
>
> > After this, we can no longer spin on any locks with preempt enabled,
> > and cannot reenable interrupts when spinning on an irq safe lock, because
> > at that point we
Greg Trounson <[EMAIL PROTECTED]> writes:
> mount [fs] -o remount,noatime,nodiratime
nodiratime is implied in noatime.
> I get a compile time of 1m23.368s, a mere 6% improvement.
6% is nothing to sneeze at. A lot of optimizations would kill for less
-Andi
-
To unsubscribe from this list: send
On Wednesday 08 August 2007 23:01, Christoph Lameter wrote:
> From: Mike Travis <[EMAIL PROTECTED]>
Why does Mike not submit his patches by himself?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Thu, 9 Aug 2007, Greg Trounson wrote:
Measurements show that noatime helps 20-30% on regular desktop workloads,
easily 50% for kernel builds and much more than that (in excess of 100%)
for file-read-intense workloads. We cannot just walk past such a _huge_
performance impact so easily
Ingo Molnar wrote:
* Alan Cox <[EMAIL PROTECTED]> wrote:
People just need to know about the performance differences - very
few realise its more than a fraction of a percent. I'm sure Gentoo
will use relatime the moment anyone knows its > 5% 8)
noatime,nodiratime gave 50% of wall-clock kernel
> --- a/Documentation/lguest/lguest.c
> +++ b/Documentation/lguest/lguest.c
> @@ -46,7 +46,7 @@ typedef uint32_t u32;
> typedef uint16_t u16;
> typedef uint8_t u8;
> #include "../../include/linux/lguest_launcher.h"
> -#include "../../include/asm-i386/e820.h"
> +#include
Chris Snook <[EMAIL PROTECTED]> wrote:
>
> Some architectures currently do not declare the contents of an atomic_t to be
> volatile. This causes confusion since atomic_read() might not actually read
> anything if an optimizing compiler re-uses a value stored in a register, which
> can break code
On 8/8/07, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> Add a generic lg.h file to call the architecture specific one.
>
> diff --git a/drivers/lguest/lg.h b/drivers/lguest/lg.h
> new file mode 100644
> index 000..4c4356e
> --- /dev/null
> +++ b/drivers/lguest/lg.h
> @@ -0,0 +1,3 @@
> +#ifdef
Andrew Morton wrote:
On Wed, 08 Aug 2007 14:10:15 -0700
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
Why isn't this easily fixable by just adding an additional dirty
flag that says atime has changed? Then we only cause a write
when we remove the inode from the inode cache, if only atime
is
>
> I was thinking along the same lines as well, but I really didn't know how
> important all that code was for waiting for the next irq slice. I'm not time
> expert, but I would imagine we would resynchronize correctly in the future
> after
> this code path?
The idea is to just have the apic
On 8/8/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Thursday 09 August 2007 01:17:19 Aaron Durbin wrote:
> > In setup_APIC_timer with the HPET in use, a condition can arise while
> > waiting for the next irq slice to expire on the HPET which will either
> > cause an NMI watchdog to fire or a 3
On Thu, 2007-08-09 at 02:24 +0200, Andi Kleen wrote:
> Not sure what's best. Ok using a normal export is easiest and not
> that big an issue.
Yeah, there's also been talk of breaking up paravirt_ops into multiple
structs by area, which would lead naturally into finer-grained export
control.
Make a i386 directory in the lguest directory, and move the lg.h into
it. This will clear the way for other archs to have their own lg.h
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/lguest/i386/lg.h | 300 ++
drivers/lguest/lg.h
The hvc_lguest uses __pa in the const initialization.
In some architectures, __pa() is not constant so this fails in compiles.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/char/hvc_lguest.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git
Move the io struct into the lg.h file since the io.c is generic to other
architectures.
Also added a proper ifdef for the generic lg.h.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/lguest/i386/lg.h | 11 ++-
drivers/lguest/lg.h | 16
2 files
The lguest_dma_info is also generic across architectures.
Move it to the generic lg.h
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/lguest/i386/lg.h | 11 ---
drivers/lguest/lg.h | 11 +++
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git
Add a generic lg.h file to call the architecture specific one.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/lguest/lg.h |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/lguest/lg.h b/drivers/lguest/lg.h
new file mode 100644
index
Have the lguest launcher include e820.h via asm/e820.h instead of explicitly
saying i386.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
Documentation/lguest/lguest.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/lguest/lguest.c
Hi all,
I've been working on lguest64 and in order to do this, I had to move
a lot of the i386 specific out of the way. Well, the lguest64 port
is still not ready to display, but before Rusty makes too many changes
I would like this in upstream so I don't have to keep repeating my
changes :-)
On 8/8/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:
> > So, unless I'm very wrong, it only makes sense to talk about not
> > supporting large pages in the guest level. But it is not a
> > paravirt_ops problem.
>
> Some MMU-related PV techiniques (including Xen, and direct paging mode
> for
Glauber de Oliveira Costa wrote:
> On 8/8/07, Nakajima, Jun <[EMAIL PROTECTED]> wrote:
> > Glauber de Oliveira Costa wrote:
> > > Hi folks,
> > >
> > > After some time away from it, and a big rebase as a consequence,
here is
> > > the updated version of paravirt_ops for x86_64, heading to
Some uses of printk are missing KERN_ on the second
and subsequent lines.
For instance:
printk(KERN_INFO "line1: %d\nline2: %d\n", val1, val2);
Line1 is marked log_level: info
Line2 is marked log_level: unknown
Some lines have trailing spaces after \n, removed where appropriate.
On Thursday 09 August 2007 01:17:19 Aaron Durbin wrote:
> In setup_APIC_timer with the HPET in use, a condition can arise while
> waiting for the next irq slice to expire on the HPET which will either
> cause an NMI watchdog to fire or a 3 minute busy loop if the NMI
> watchdog is disabled.
>
>
On Thursday 09 August 2007 01:18:57 Rusty Russell wrote:
> On Wed, 2007-08-08 at 11:49 -0300, Glauber de Oliveira Costa wrote:
> > On 8/8/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > > +EXPORT_SYMBOL(paravirt_ops);
> > >
> > > Definitely _GPL at least.
> > Sure.
>
> We ended up making it
On Wed, Aug 08, 2007 at 06:24:47PM +0200, J??rn Engel wrote:
> --- linux-2.6.21logfs/include/linux/Kbuild~logfs 2007-08-08
> 02:57:37.0 +0200
> +++ linux-2.6.21logfs/include/linux/Kbuild2007-08-08 02:57:37.0
> +0200
> @@ -101,6 +101,7 @@ header-y += jffs2.h
> header-y
On Wed, Aug 08, 2007 at 05:08:44PM -0400, Chris Snook wrote:
> Heiko Carstens wrote:
> >On Wed, Aug 08, 2007 at 03:21:31AM -0700, David Miller wrote:
> >>From: Heiko Carstens <[EMAIL PROTECTED]>
> >>Date: Wed, 8 Aug 2007 11:33:00 +0200
> >>
> >>>Just saw this while grepping for atomic_reads in a
Removing the getty from initd did the trick.
And you're right AVR is disabled by the kernel
found the code in ./arch/powerpc/platforms/embedded6xx/ls_uart.c
Tkank you
Guennadi Liakhovetski wrote:
On Thu, 9 Aug 2007, Oncaphillis wrote:
I hope I found the the misconfigured part. I
On Thu, 9 Aug 2007 01:31:20 +0300
Mikko Rapeli <[EMAIL PROTECTED]> wrote:
> Since 2.6.23-rc1 I can't boot an old k6 (with a funky IDE drive worth testing
> with libata). The boot hangs without a sound or letter prints on the
> screen right after grub, while 2.6.22.1 works fine.
Try adding the
On Wed, 2007-08-08 at 11:49 -0300, Glauber de Oliveira Costa wrote:
> On 8/8/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > > +EXPORT_SYMBOL(paravirt_ops);
> >
> > Definitely _GPL at least.
> Sure.
We ended up making it EXPORT_SYMBOL in i386 because every driver wants
to save and restore interrupt
I have the latest BIOS update for my laptop which is buggy I suppose.
There has been only one update this year if my memory serves me
correctly. Is there any hope to fix this or am I at the mercy of the
hardware vendor which apparenlty doesn't look like they will release
another patch this year.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Mortensen wrote:
> I'm wondering if any resolution to this particular bug? I see this
> exact kernel bug in copying large data sets (40GB+), and can reproduce
> fairly well. Running reiserfsck produces this message:
>
> "Zero bit found in
On 09/08/2007, Chris Snook <[EMAIL PROTECTED]> wrote:
> Jesper Juhl wrote:
> > On 09/08/2007, Chris Snook <[EMAIL PROTECTED]> wrote:
> >> From: Chris Snook <[EMAIL PROTECTED]>
> >>
> >> Some architectures currently do not declare the contents of an atomic_t to
> >> be
> >> volatile. This causes
Ingo Molnar and group,
First, RT/RR tasks are not deprecated. This
change simply removes sched overhead while
only 1 RT/RR task is runable per rq.
The code size increase is minor and is a very
straightforward change..
THUS...
My assumption is / was to hand you/Ingo Molnar this change
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Mortensen wrote:
> I'm wondering if any resolution to this particular bug? I see this
> exact kernel bug in copying large data sets (40GB+), and can reproduce
> fairly well. Running reiserfsck produces this message:
>
> "Zero bit found in
Lennert Buytenhek wrote:
On Wed, Aug 08, 2007 at 07:07:33PM -0400, Chris Snook wrote:
From: Chris Snook <[EMAIL PROTECTED]>
Some architectures currently do not declare the contents of an atomic_t to be
volatile. This causes confusion since atomic_read() might not actually read
anything if an
On Wed, 8 Aug 2007, Lee Schermerhorn wrote:
> It'll take me a while to absorb the patch, so I'll just ask: Where does
> the zonelist for the argument come from? If the the bind policy
> zonelist is removed, then does it come from a node? There'll be only
Right.
> one per node with your other
> On the other hand, given that we've always said that closed-source stuff in
> userspace is OK, the only way to not let *that* horse out of the barn is to
> not merge UIO at all.
It really makes no difference whether it is merged or not. The test is
"derivative work" and not 'linking'.
A user
On Wed, 8 Aug 2007, Mel Gorman wrote:
>
> > For various policies, the arguments would look like this:
> > Policy start node nodemask
> >
> > default local node cpuset_current_mems_allowed
> >
> > preferred preferred_node cpuset_current_mems_allowed
> >
>
Jesper Juhl wrote:
On 09/08/2007, Chris Snook <[EMAIL PROTECTED]> wrote:
From: Chris Snook <[EMAIL PROTECTED]>
Some architectures currently do not declare the contents of an atomic_t to be
volatile. This causes confusion since atomic_read() might not actually read
anything if an optimizing
Thanks. Queued up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 8 Aug 2007, Mel Gorman wrote:
> The zone_id is the one I'm really interested in. It looks like the most
> promising optimisation for avoiding zone_idx in the hotpath.
Certainly the highest priority. However, if the nodeid could be coded in
then we may be able to also avoid the
On Wed, 8 Aug 2007, Mel Gorman wrote:
> I'll revisit it again just in case but for now I'd rather not get
> sidetracked from the patchset at hand.
Sure. This is more long term.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Wed, Aug 08, 2007 at 07:07:33PM -0400, Chris Snook wrote:
> From: Chris Snook <[EMAIL PROTECTED]>
>
> Some architectures currently do not declare the contents of an atomic_t to be
> volatile. This causes confusion since atomic_read() might not actually read
> anything if an optimizing
This patch fixes the following 2.6.23 regression:
<-- snip -->
...
scripts/kconfig/conf -d arch/cris/Kconfig
arch/cris/Kconfig:183: can't open file "drivers/cdrom/Kconfig"
make[2]: *** [defconfig] Error 1
<-- snip -->
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
On Wed, Aug 08, 2007 at 11:41:06PM +0200, Andreas Gruenbacher wrote:
> Lookup or not doesn't actually matter. Think of fchdir(2): it does a
> permission check, and it should also pass down the LOOKUP_CHDIR flag.
fchdir per defintion doesn't do any lookup, and it should not pretend to be
doing
On 09/08/2007, Chris Snook <[EMAIL PROTECTED]> wrote:
> From: Chris Snook <[EMAIL PROTECTED]>
>
> Some architectures currently do not declare the contents of an atomic_t to be
> volatile. This causes confusion since atomic_read() might not actually read
> anything if an optimizing compiler
In setup_APIC_timer with the HPET in use, a condition can arise while
waiting for the next irq slice to expire on the HPET which will either
cause an NMI watchdog to fire or a 3 minute busy loop if the NMI
watchdog is disabled.
The HPET comparator and the counter keep incrementing during its
1 - 100 of 1192 matches
Mail list logo
