Dan Hecht wrote:
> Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
> ours for reference (please excuse any formating issues); it's also
> lean. We'll send out a proper patch later after some more testing:
So the interrupt side of the clockevent comes through the virtual apic?
On Wed, 2007-03-07 at 09:41 -0800, Jeremy Fitzhardinge wrote:
> Other hypervisors may take other approaches, depending on what the real
> underlying hardware is and the real requirements. One could imagine a
> hypervisor exposing an hpet mapping, for example, or just having some
> kind of complete
On Wed, 2007-03-07 at 12:11 -0800, Jeremy Fitzhardinge wrote:
> Dan Hecht wrote:
> > Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
> > ours for reference (please excuse any formating issues); it's also
> > lean. We'll send out a proper patch later after some more testing:
>
>
On 03/07/2007 12:11 PM, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
ours for reference (please excuse any formating issues); it's also
lean. We'll send out a proper patch later after some more testing:
So the interrupt side of
On 03/07/2007 12:57 PM, Thomas Gleixner wrote:
On Wed, 2007-03-07 at 12:11 -0800, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
ours for reference (please excuse any formating issues); it's also
lean. We'll send out a proper patc
Thomas Gleixner wrote:
> I tend to disagree. The clockevents infrastructure was designed to cope
> with the existing mess of real hardware. The discussion over the last
> days exposed me to even more exotic designs than the hardware vendors
> were able to deliver until now.
>
It's a different b
Dan Hecht wrote:
> Are you saying you would prefer we create our own irq handler
> something like this rather than using the standard i386 handlers?
>
> irqreturn_t vmi_timer_interrupt(int irq, void *dev_id)
> {
>local_event->event_handler(local_event);
>return IRQ_HANDLED;
> }
>
> ?? That
On Wed, 2007-03-07 at 12:49 -0800, Dan Hecht wrote:
> On 03/07/2007 12:11 PM, Jeremy Fitzhardinge wrote:
> > Dan Hecht wrote:
> >> Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
> >> ours for reference (please excuse any formating issues); it's also
> >> lean. We'll send out a
On Wed, 2007-03-07 at 13:02 -0800, Dan Hecht wrote:
> On 03/07/2007 12:57 PM, Thomas Gleixner wrote:
> > On Wed, 2007-03-07 at 12:11 -0800, Jeremy Fitzhardinge wrote:
> >> Dan Hecht wrote:
> >>> Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
> >>> ours for reference (please exc
On Wed, 2007-03-07 at 11:49 -0800, Dan Hecht wrote:
> Jeremy, I saw you sent out the Xen version earlier, thanks. Here's ours
> for reference (please excuse any formating issues); it's also lean.
> We'll send out a proper patch later after some more testing:
Ah. Bitching loud enough speeds thin
On 03/07/2007 01:19 PM, Thomas Gleixner wrote:
On Wed, 2007-03-07 at 13:02 -0800, Dan Hecht wrote:
On 03/07/2007 12:57 PM, Thomas Gleixner wrote:
On Wed, 2007-03-07 at 12:11 -0800, Jeremy Fitzhardinge wrote:
Dan Hecht wrote:
Jeremy, I saw you sent out the Xen version earlier, thanks. Here's
On Wed, 2007-03-07 at 13:07 -0800, Jeremy Fitzhardinge wrote:
> Thomas Gleixner wrote:
> > I tend to disagree. The clockevents infrastructure was designed to cope
> > with the existing mess of real hardware. The discussion over the last
> > days exposed me to even more exotic designs than the hardw
On 03/07/2007 01:40 PM, Thomas Gleixner wrote:
On Wed, 2007-03-07 at 13:07 -0800, Jeremy Fitzhardinge wrote:
That would certainly be ideal. We'll look at the xen, vmi, lguest and
kvm paravirtualized time models and see how much they really have in
common. I'm a bit curious about how vmi's time
On 03/07/2007 01:21 PM, Thomas Gleixner wrote:
On Wed, 2007-03-07 at 11:49 -0800, Dan Hecht wrote:
Jeremy, I saw you sent out the Xen version earlier, thanks. Here's ours
for reference (please excuse any formating issues); it's also lean.
We'll send out a proper patch later after some more tes
On 03/07/2007 12:40 PM, Thomas Gleixner wrote:
Real hardware copes well with relative deltas for the events, even when
it is match register based. I thought long about the support for
absolute expiry values in cycles and decided against them to avoid that
math hackery, which you folks now demand.
On Wed, 2007-03-07 at 13:42 -0800, Dan Hecht wrote:
> On 03/07/2007 12:40 PM, Thomas Gleixner wrote:
> > Real hardware copes well with relative deltas for the events, even when
> > it is match register based. I thought long about the support for
> > absolute expiry values in cycles and decided agai
Thomas Gleixner wrote:
> This is tinkering of the best. My understanding of the paravirt
> discussion at Kernel Summit was, that paravirt ops are exactly there to
> prevent the above random hackery in the kernel and to allow _ALL_
> hypervisors to interact via a sane interface inside of the kernel.
On Wed, 2007-03-07 at 13:34 -0800, Dan Hecht wrote:
> On 03/07/2007 01:40 PM, Thomas Gleixner wrote:
> > On Wed, 2007-03-07 at 13:07 -0800, Jeremy Fitzhardinge wrote:
> > That would certainly be ideal. We'll look at the xen, vmi, lguest and
> >> kvm paravirtualized time models and see how much the
Thomas Gleixner wrote:
Simply because you _ABUSE_ timer_init_hook() to set it up. Keep it self
contained and do not impose restrictions on the kernel core code, which
we have to maintain.
But time_init_hook is supposed to be abused. That is its purpose - to
be a hook for different time dev
On Wed, 2007-03-07 at 14:17 -0800, Zachary Amsden wrote:
> Thomas Gleixner wrote:
> > Simply because you _ABUSE_ timer_init_hook() to set it up. Keep it self
> > contained and do not impose restrictions on the kernel core code, which
> > we have to maintain.
> >
>
> But time_init_hook is suppos
On 03/07/2007 02:31 PM, Thomas Gleixner wrote:
Please make these things self contained and not relying on whatever
time_init_hook() contains.
Fixing up the code to do this now
thanks,
Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 2007-03-07 at 14:05 -0800, Jeremy Fitzhardinge wrote:
> Thomas Gleixner wrote:
> > This is tinkering of the best. My understanding of the paravirt
> > discussion at Kernel Summit was, that paravirt ops are exactly there to
> > prevent the above random hackery in the kernel and to allow _ALL
Thomas Gleixner wrote:
On the other hand we yet see things like:
/* We use normal irq0 handler on cpu0. */
time_init_hook();
Which is just reaching into the kernel code directly and does not handle
the clock event interrupt self contained. clockevents is not bound to
IRQ0 and th
Thomas Gleixner wrote:
> Still there is a difference between using existing kernel interfaces and
> abusing them in a way which makes modifications to the core kernel code
> hard and unmaintainable. See below.
>
I completely agree. "Using the kernel interfaces" doesn't mean "this
random hack h
Zachary Amsden wrote:
> Xen needs pieces of it too, but very select pieces for SMP boot.
We do? Send the SMP Xen code over, because I don't have it here.
Thanks,
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More maj
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Xen needs pieces of it too, but very select pieces for SMP boot.
We do? Send the SMP Xen code over, because I don't have it here.
s/do/will (smpboot.c)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
> Yep, the tsc has myriad problems; for Xen its the best of a bad lot.
> Unfortunately in 10 years no clearly better alternative has appeared;
> maybe in 10 years there will be one. It might even be the tsc.
TSC is essentially unusable for any kind of time related work. And I'd
disagree about th
From: Rojhalat Ibrahim <[EMAIL PROTECTED]>
We get the following compiler error:
CC arch/ppc/kernel/ppc_ksyms.o
arch/ppc/kernel/ppc_ksyms.c:275: error: '__mtdcr' undeclared here (not in a
function)
arch/ppc/kernel/ppc_ksyms.c:275: warning: type defaults to 'int' in declaration
of '__mtdc
From: Joerg Dorchain <[EMAIL PROTECTED]>
Undocumented...
Signed-off-by: Joerg Dorchain <[EMAIL PROTECTED]>
Acked-by: Achim Leubner <[EMAIL PROTECTED]>
Cc: James Bottomley <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
-
On Wed, Feb 28 2007, Andre Noll wrote:
> On 16:18, Andre Noll wrote:
>
> > With 2.6.21-rc2 I am unable to reproduce this BUG message. However,
> > writing to both raid systems at the same time via lvm still locks up
> > the system within minutes.
>
> Screenshot of the resulting kernel panic:
>
>
On Wed, 7 Mar 2007 18:09:55 +0100 Andre Noll <[EMAIL PROTECTED]> wrote:
> On 20:39, Andrew Morton wrote:
> > On Wed, 28 Feb 2007 16:37:22 +0100 Andre Noll <[EMAIL PROTECTED]> wrote:
> >
> > > On 16:18, Andre Noll wrote:
> > >
> > > > With 2.6.21-rc2 I am unable to reproduce this BUG message. How
On Wed, 2007-03-07 at 11:45 -0800, Andrew Morton wrote:
> On Wed, 7 Mar 2007 18:09:55 +0100 Andre Noll <[EMAIL PROTECTED]> wrote:
>
> > On 20:39, Andrew Morton wrote:
> > > On Wed, 28 Feb 2007 16:37:22 +0100 Andre Noll <[EMAIL PROTECTED]> wrote:
> > >
> > > > On 16:18, Andre Noll wrote:
> > > >
From: Chris Lesiak <[EMAIL PROTECTED]>
This patch fixes a bug in the cleanup of an spi_bitbang bus. The
workqueue associated with the bus was destroyed before the call to
spi_unregister_master. That meant that spi devices on that bus would be
unable to do IO in their remove method. The shutdown
On Wed, Mar 07, 2007 at 06:38:32PM -0500, Robert P. J. Day wrote:
>
> Replace the apparently misspelled preprocessor variable "PRINTK"
> with "CONFIG_PRINTK".
this looks wrong.
> diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
> index 5554ada..0c09772 100644
> --- a/drivers/md/bi
On Tue, 6 Mar 2007 00:44:08 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.21-rc2-mm2/
>
e1000 gave this on a warm boot:
http://belly.cps.unizar.es/~magallon/oops/IMG_1510.JPG
Any idea ?
--
J.A. Magallon \ Soft
On Thu, Mar 08, 2007 at 12:13:05AM +0100, Rafael J. Wysocki wrote:
> > > Well, the WARN_ON() in arch/x86_64/kernel/acpi/sleep.c:init_low_mapping()
> > > triggers every time an SMP x86_64 box is suspended to disk using the
> > > platform
> > > mode (default), which is quite annoying IMHO and u
On Thu, 8 Mar 2007 01:03:23 +0100
"J.A. Magall__n" <[EMAIL PROTECTED]> wrote:
> On Tue, 6 Mar 2007 00:44:08 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm2/
> >
>
> e1000 gave this on a warm boot:
>
> http://be
On Wed, 7 Mar 2007, Dave Jones wrote:
> On Wed, Mar 07, 2007 at 06:38:32PM -0500, Robert P. J. Day wrote:
> >
> > Replace the apparently misspelled preprocessor variable "PRINTK"
> > with "CONFIG_PRINTK".
>
> this looks wrong.
>
> > diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
> >
On 3/7/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>
> On 3/7/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>>
>> On Wed, 7 Mar 2007, Luong Ngo wrote:
>>
>>> Hi all,
>>>
>>> I am having this problem. I have a process with 2 threads created. One
>>> of the thread will keep cal
On Wed, 7 Mar 2007 16:23:15 -0800 Andrew Morton wrote:
> The below will apppear in -rc3-mm1 (hopefully later today) and it will
> hopefully fix that crash.
>
>
> From: Auke Kok <[EMAIL PROTECTED]>
>
> ---
>
> drivers/net/e1000/e1000_main.c | 66 +--
> 1 files cha
Every single non-PCI controller has been broken by this code.
pata_get_dev_handle() assumes that the passed ata_port is PCI. The
libata-core code does not do any checking. This causes everyone to
experience oopses with pata_pcmcia for example.
Multiple examples of the bug in our FC7test tree repo
Randy Dunlap wrote:
On Wed, 7 Mar 2007 16:23:15 -0800 Andrew Morton wrote:
The below will apppear in -rc3-mm1 (hopefully later today) and it will
hopefully fix that crash.
From: Auke Kok <[EMAIL PROTECTED]>
---
drivers/net/e1000/e1000_main.c | 66 +--
1 files
On 3/7/07, Lee Revell <[EMAIL PROTECTED]> wrote:
On 3/7/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
> Interruptible_sleep_on is interruptible, but for your task to
> actually be awakened and your alarm handler to get some CPU,
> it needs to be scheduled. If the BKL (big kernel lock) is
On Thu, Mar 08, 2007 at 08:30:43AM +1100, Paul Mackerras wrote:
> Sergei Shtylyov writes:
>
> > I've floowed up to my patch with such explanation. In the context of
> > an-rt
> > patch itself, it was just too clear, hence I didn't go into explanations in
> > the patch itself. :-)
>
> Well,
On Thursday, 8 March 2007 01:20, Dave Jones wrote:
> On Thu, Mar 08, 2007 at 12:13:05AM +0100, Rafael J. Wysocki wrote:
>
> > > > Well, the WARN_ON() in
> arch/x86_64/kernel/acpi/sleep.c:init_low_mapping()
> > > > triggers every time an SMP x86_64 box is suspended to disk using the
> platform
Christoph Hellwig <[EMAIL PROTECTED]> wrote on 03/07/2007 04:17:46 PM:
> On Wed, Mar 07, 2007 at 12:51:04PM -0600, Steven French wrote:
> > Is there an easy way to mirror particular patches going into the
> > cifs-2.6.git tree (which is pulled into mm) to lkml?
>
> Maybe some git expert can comm
On Tue, Mar 06, 2007 at 21:20:33 +0100, Eric Dumazet wrote:
...
> I rewrote the reciprocal_div() for i386 so that one multiply is used.
>
> static inline u32 reciprocal_divide(u32 A, u32 R)
> {
> #if __i386
> unsigned int edx, eax;
> asm("mul %2":"=a" (eax), "=d" (edx):"rm" (R), "0
the usage of the DEBUG_DRIVER preprocessor variable is a big
confusing:
$ $ grep -rw DEBUG_DRIVER *
drivers/net/sunlance.c:#undef DEBUG_DRIVER
drivers/net/a2065.c:#ifdef DEBUG_DRIVER
drivers/net/a2065.c:#ifdef DEBUG_DRIVER
drivers/net/7990.c:#ifdef DEBUG_DRIVER
drivers/net/7990.c:#ifdef DEBUG_D
Bill Irwin <[EMAIL PROTECTED]> writes:
> On Wed, Mar 07, 2007 at 04:03:17PM -0700, Eric W. Biederman wrote:
>> I think the right answer is most likely to add an extra file method or
>> two so we can remove the need for is_file_hugepages.
>> There are still 4 calls to is_file_hugepages in ipc/shm.c
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
This
This patch series implements the new signalfd() and signalfd_dequeue()
system calls. I took part of the original Linus code (and you know how
badly it can be broken :), and I added even more breakage ;)
The patch had to be almost completely changed. This patch allows multiple
signalfd to listen f
This patch wire the signalfd system calls to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
--- linux-2.6.20.ep2.orig/arch/i386/kernel/syscall_table.S
This patch wire the signalfd system calls to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/include/asm-x86_64/unistd.h
===
--- linux-2.6.20.ep2.orig/include/asm-x86_64/unistd.h 2007-
This patch implement the necessary compat code for the signalfd system calls.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c 2007-03-07 13:28:39.0
On 3/7/07, Linus Torvalds <[EMAIL PROTECTED]> wrote
Yeah, I'm not at all surprised. Any implementation of "prefetch" that
doesn't just turn into a no-op if the TLB entry doesn't exist (which makes
them weaker for *actual* prefetching) will generally have a hard time with
a NULL pointer. Exactly b
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> It should give us a better clue which sysfs file is causing the oops.
This BUG happened during boot-up! The only USB device I have is a pwc webcam:
$ /sbin/lsusb
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002 Device 001: I
On Wed, Mar 07, 2007 at 02:12:16PM -0800, Dave Hansen wrote:
> I'm seeing weird hangs running ltp on 2.6.21-rc2-mm2. It manifests
> itself by the waitpid06 test in LTP hanging. This is very, very
> reproducible in about 5 seconds by adding '-s wait' to the ltp command
> line.
>
> I see 4 waitpid
On Wednesday March 7, [EMAIL PROTECTED] wrote:
>
> Replace the apparently misspelled preprocessor variable "PRINTK"
> with "CONFIG_PRINTK".
No, it is meant to be "PRINTK".
It dates way way back before my time, but presumably the idea was you
could -DPRINTK=something and if you didn't do that, i
On Wed, 7 Mar 2007 12:26:42 +1100
Con Kolivas <[EMAIL PROTECTED]> wrote:
> What follows is the same patch series that constitutes the RDSL "Rotating
> Staircase DeadLine" cpu scheduler resynced for 2.6.21-rc2-mm2.
Big oops early in boot on x86_64 SMP, in rq_bitmap_error+0x97/0x9f.
I stubbed it
On 3/7/07, Alan Cox <[EMAIL PROTECTED]> wrote:
The right way IMHO would be to do the work that was done for pread/pwrite
and implement preadv/pwritev. The moment you want to do atomic things
with the file->f_pos instead of doing it with a local passed pos value it
gets ugly.. why do you need to d
I wrote:
I didn't see any clean way to intersperse overwrites and appends to a
record-structured file without using vfs_llseek, which steps on f_pos.
The context, of course, is an attempt to fix -ENOPATCH with regard to
the netlink-based AIO submission scheme I outlined a couple of days
ago. :
Hi,
On Tuesday 06 March 2007 10:29, Christoph Hellwig wrote:
> PAGE_SIZE should not be available at all. Please use getpagesize()
> instead.
While I agree, NBPG is a bit of a problem, although it's only needed for aout
coredumps AFAICT, but still needed to compile e.g. gdb.
bye, Roman
-
To un
At Wed, 07 Mar 2007 17:26:50 +0300,
Sergei Shtylyov wrote:
>
> Tsutomu OWA wrote:
> > CONFIG_MCOUNT, CONFIG_LATENCY_TRACE and other tracing options nor
> > CONFIG_GENERIC_TIME,
>
> There is PowerPC genTOD patch and it's incorporated into -rt (don't know
> it works for Cell) but it breaks
On Mar 07, 2007, at 20:25:14, Michael K. Edwards wrote:
On 3/7/07, Linus Torvalds <[EMAIL PROTECTED]> wrote
In general, using software prefetching is just a stupid idea, unless
- the prefetch really is very strict (ie for a linked list you do
exactly the above kinds of things to make sure th
On Wed, 7 Mar 2007 17:43:45 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 7 Mar 2007 12:26:42 +1100
> Con Kolivas <[EMAIL PROTECTED]> wrote:
>
> > What follows is the same patch series that constitutes the RDSL "Rotating
> > Staircase DeadLine" cpu scheduler resynced for 2.6.21-rc2-mm
On Wed, 07 Mar 2007 12:28:11 -0700 [EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Below is an additional set of warnings that should help debug this.
> The old code just got lucky that it triggered a warning when this happens.
>
> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
> index 01869b1
All comments have been taken care of.
Description:
A file_operations structure variable called loop_fops is initialised with
the default block device file operations (def_blk_fops).
The mmap operation is overriden with a new function called loop_file_mmap.
A vm_operations structure variable
On Wed, 7 Mar 2007, Michael K. Edwards wrote:
>
> People's prejudices against prefetch instructions are sometimes
> traceable to the 3DNow! prefetch(w) botch, which some processors
> "support" as no-ops and others are too aggressive about (Opteron
> prefetches are reputed to be "strong", i. e.,
Bill Huey (hui) writes:
> The places that need to be reverted to raw spinlocks are generally either
> acquired by function calls that allocate the spinlock at a terminal of the
> kernel's lock graph or isolated from other callers completely (parts of the
> timer for logic for instance). It's all a
> From: Andrew Morton
> Newsgroups: gmane.linux.kernel
> Subject: Re: [PATCH -mm] Blackfin: blackfin i2c driver
> Date: Tue, 6 Mar 2007 23:45:29 -0800
[]
> On Wed, 07 Mar 2007 15:39:27 +0800 "Wu, Bryan" <[EMAIL PROTECTED]> wrote:
>
>> Thanks a lot, could you please give me a script just to kill thi
On Thu, Mar 08, 2007 at 02:26:47PM +1100, Paul Mackerras wrote:
> Bill Huey (hui) writes:
>
> > The places that need to be reverted to raw spinlocks are generally either
> > acquired by function calls that allocate the spinlock at a terminal of the
> > kernel's lock graph or isolated from other ca
On Wed, 7 Mar 2007 18:54:30 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 7 Mar 2007 17:43:45 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 7 Mar 2007 12:26:42 +1100
> > Con Kolivas <[EMAIL PROTECTED]> wrote:
> >
> > > What follows is the same patch series that constitu
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
- This is the same as 2.6.21-rc3-mm1, except Con's CPU scheduler changes
were dropped.
This is for A/B comparison purposes, and because those changes crashed on
one test setup.
Changes since 2.6.21-
Temporarily at
http://userweb.kernel.org/~akpm/2.6.21-rc3-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm1/
- The wireless changes in here need a lot of testers, please. It is major
rework.
Of course the config files
On 08/03/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 7 Mar 2007 17:43:45 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 7 Mar 2007 12:26:42 +1100
> Con Kolivas <[EMAIL PROTECTED]> wrote:
>
> > What follows is the same patch series that constitutes the RDSL "Rotating
> > Stairc
Hi Linus,
Please consider pulling from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive fix for AUX IRQ delivery test that causes missing keyboards
on some boxes without PS/
While I agree, NBPG is a bit of a problem, although it's only needed for aout
coredumps AFAICT, but still needed to compile e.g. gdb.
Well then how does gdb deal with ia64? because PAGE_SIZE and friends
aren't available for that arch same with ppc.
Looking at the gdb code they do have places wh
On Thursday 08 March 2007 15:15, Andrew Morton wrote:
> On Wed, 7 Mar 2007 18:54:30 -0800 Andrew Morton <[EMAIL PROTECTED]>
wrote:
> > On Wed, 7 Mar 2007 17:43:45 -0800 Andrew Morton
<[EMAIL PROTECTED]> wrote:
> > > On Wed, 7 Mar 2007 12:26:42 +1100
> > >
> > > Con Kolivas <[EMAIL PROTECTED]> wro
Adrian Bunk wrote:
> On Tue, Mar 06, 2007 at 12:44:08AM -0800, Andrew Morton wrote:
>> ...
>> Changes since 2.6.20-rc2-mm1:
>> ...
>> git-mmc.patch
>> ...
>> git trees
>> ...
>
> mmc_deselect_cards() is no longer used.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
Indeed, but it's prob
On Wed, Mar 07, 2007 at 01:02:14PM -0800, Andrew Morton wrote:
> On Wed, 7 Mar 2007 12:31:21 +0100
> Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > Index: linux-2.6/mm/memory.c
> > ===
> > --- linux-2.6.orig/mm/memory.c
> > +++ linux-2.
(cc restored. Please always do reply-to-all)
> On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] wrote:
> On Wednesday 28 February 2007 17:19, Sid Boyce wrote:
> > openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to
> > require a password to unlock, but it asks for password.
> On Thu, 8 Mar 2007 16:25:05 +1100 Con Kolivas <[EMAIL PROTECTED]> wrote:
> > It also boots OK on a very similar but somewhat older Nocona machine.
> > Perhaps due to config changes:
> > http://userweb.kernel.org/~akpm/ck/config-ok.txt
>
> Ok I just remembered that not only did I expect the cpu
On Wed, 7 Mar 2007 12:00:04 +
Ash Milsted <[EMAIL PROTECTED]> wrote:
> On Sun, 4 Mar 2007 14:23:50 +
> Ash Milsted <[EMAIL PROTECTED]> wrote:
>
> > On Sat, 3 Mar 2007 15:14:24 +
> > Ash Milsted <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > > With 2.6.21-rc2-git1 I have a problem with
On Wed, 7 Mar 2007, Ash Milsted wrote:
>
> So, I tracked this down to 2.6.21-git7, the first snapshot that gives me
> this problem.
Hmm. There is no "2.6.21-git7" (that would be the seventh nightly snapshot
after 2.6.21 is released, which hasn't happened yet!).
Do you mean that it happens bet
On 3/7/07, Ash Milsted <[EMAIL PROTECTED]> wrote:
On Wed, 7 Mar 2007 12:00:04 +
Ash Milsted <[EMAIL PROTECTED]> wrote:
> On Sun, 4 Mar 2007 14:23:50 +
> Ash Milsted <[EMAIL PROTECTED]> wrote:
>
> > On Sat, 3 Mar 2007 15:14:24 +
> > Ash Milsted <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
Le mardi 06 mars 2007 à 16:15 -0800, Andrew Morton a écrit :
> On Tue, 6 Mar 2007 15:36:29 -0800
> [EMAIL PROTECTED] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=8136
> So rc2-mm2 panics due to "MP-BIOS bug: 8254 timer not connected to IO-APIC"
> and
> rc2-mm1 does not.
>
> Could be
On Wed, 7 Mar 2007, Jeff Garzik wrote:
>
> Adrian Bunk wrote:
> > Subject: AT keyboard only works with pci=noacpi
> > References : http://lkml.org/lkml/2007/3/3/68
> > Submitter : Ash Milsted <[EMAIL PROTECTED]>
> > Status : unknown
>
> sounds like a BIOS bug, even though it appears to
On Wed, 7 Mar 2007, Ash Milsted wrote:
>
> Anyway, here's the bootlog for Dmitry from a boot with broken keyboard
> (2.6.21-rc3):
The non-working setup doesn't get any interrupts back, and thus doesn't
see the ACK for the "\xd4\xed" command.
It really looks interrupt-related (especially cons
From: NeilBrown <[EMAIL PROTECTED]>
There are two errors that can lead to recovery problems with raid10
when used in 'far' more (not the default).
Due to a '>' instead of '>=' the wrong block is located which would
result in garbage being written to some random location, quite
possible outside th
From: Neil Brown <[EMAIL PROTECTED]>
md/bitmap tracks how many active write requests are pending on blocks
associated with each bit in the bitmap, so that it knows when it can
clear the bit (when count hits zero).
The counter has 14 bits of space, so if there are ever more than 16383,
we cannot c
From: Magnus Damm <[EMAIL PROTECTED]>
Kexec support for 2.6.20 on ia64 does not build properly using a config
made up by CONFIG_SMP=n and CONFIG_HOTPLUG_CPU=n:
CC arch/ia64/kernel/machine_kexec.o
arch/ia64/kernel/machine_kexec.c: In function `machine_shutdown':
arch/ia64/kernel/machine_ke
From: Pavel Roskin <[EMAIL PROTECTED]>
In the bcm43xx interrupt handler, sanity checks are wrongly done before the
verification that the interrupt is for the bcm43xx.
Signed-off-by: Pavel Roskin <[EMAIL PROTECTED]>
Signed-off-by: Larry Finger <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman
On Wednesday 07 March 2007 16:50, Dmitry Torokhov wrote:
> On 3/7/07, Ash Milsted <[EMAIL PROTECTED]> wrote:
> >
> > So, I tracked this down to 2.6.21-git7, the first snapshot that gives me
> > this problem. Tellingly it does contain an input tree merge. I would git
> > bisect
> > but I don't have
On Mar 7 2007 10:20, dean gaudet wrote:
>>> http://gentoo-wiki.com/HOWTO_Install_on_Software_RAID#Write-intent_bitmap
>>
>> That information has been extremely useful. Thanks a
>> lot. I fund a command to do the bitmap internal after
>> the array was made so I added that. Seems like some of
>> th
The vmx code currently treats the guest's sysenter support msrs as 32-bit
values, which breaks 32-bit compat mode userspace on 64-bit guests. Fix by
using the native word width of the machine.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/vmx.c |8
1 files changed, 4
Otherwise, the core module thinks the arch module is loaded, and won't
let you reload it after you've fixed the bug.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/kvm/kvm_main.c b/driver
This patchset contains fixes I plan to submit pre 2.6.21. One
improves cleanup on module load failures, while the other fixes guest
failures in compat mode (32-bit guest process on a 64-bit guest kernel).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
On 3/7/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote:
All that being said, if it were going to save space without overly
complicating things I'm actually not opposed to using nsproxy, but it
If space-saving is the main issue, then the latest version of my
containers patches uses just a single
Quoting Paul Menage ([EMAIL PROTECTED]):
> On 3/7/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote:
> >
> >All that being said, if it were going to save space without overly
> >complicating things I'm actually not opposed to using nsproxy, but it
>
> If space-saving is the main issue, then the latest
On Wed, 2007-03-07 at 15:59 -0600, Serge E. Hallyn wrote:
> Space saving was the only reason for nsproxy to exist.
>
> Now of course it also provides the teensiest reduction in # instructions
> since every clone results in just one reference count inc for the
> nsproxy rather than one for each nam
501 - 600 of 712 matches
Mail list logo
