On Wed, 28 Feb 2007 09:34:10 -0800
[EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8100
>
>Summary: dynticks makes ksoftirqd1 use unreasonable amount of cpu
> time
> Kernel Version: 2.6.21-rc2
> Status: NEW
>
On Wednesday 28 February 2007 15:21, Mike Galbraith wrote:
> (hrmph. having to copy/paste/try again. evolution seems to be broken..
> RCPT TO <[EMAIL PROTECTED]> failed: Cannot resolve your domain
> {mp049} ..caused me to be unable to send despite receipts being disabled)
Apologies for mangling
From: Christoph Lameter <[EMAIL PROTECTED]>
Date: Wed, 28 Feb 2007 11:20:44 -0800 (PST)
> V2->V3
> - Debugging and diagnostic support. This is runtime enabled and not compile
> time enabled. Runtime debugging can be controlled via kernel boot options
> on an individual slab cache basis or
From: Ingo Molnar <[EMAIL PROTECTED]>
add the arch specific bits of syslet/threadlet support to x86_64.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
---
arch/x86_64/Kconfig|4 ++
arch/x86_64/ia32/ia32entry.S | 20 ++-
arch/x86_64/kernel/entry.S | 72
On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote:
> On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
> Gerhard Mack <[EMAIL PROTECTED]> wrote:
>
>
> > > In another thread, I think they were saying it was either a SATA chipset
> > > driver bug, or a problem in libata core.
> >
> > I also have an
> On Wed, Feb 28, 2007 at 12:36:25PM -0500, Dave Jones wrote:
>> +#ifdef __powerpc__
>
> Is __powerpc__ defined when cross compiling? I'd rather use
> CONFIG_PMAC_BACKLIGHT instead of it.
Agree with this too.
Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
From: Ingo Molnar <[EMAIL PROTECTED]>
mark clone() and fork() as not available for async execution.
Both need an intact user context beneath them to work.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/kernel/ioport.c |6
From: Arjan van de Ven <[EMAIL PROTECTED]>
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two (future) optimizations:
1) allocate the right size for the actual cpu rather than 512 bytes always
2)
From: Ingo Molnar <[EMAIL PROTECTED]>
wire up the new syslet / async system call syscalls and make it
thus available to user-space.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |6 ++
From: Ingo Molnar <[EMAIL PROTECTED]>
enable CONFIG_ASYNC_SUPPORT on x86.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/Kconfig |4
1 file changed, 4 insertions(+)
Index: linux/arch/i386/Kconfig
From: Ingo Molnar <[EMAIL PROTECTED]>
add the create_async_thread() way of creating kernel threads:
these threads first execute a kernel function and when they
return from it they execute user-space.
An architecture must implement this interface before it can turn
CONFIG_ASYNC_SUPPORT on.
From: Ingo Molnar <[EMAIL PROTECTED]>
add the move_user_context() method to move the user-space
context of one kernel thread to another kernel thread.
User-space might notice the changed TID, but execution,
stack and register contents (general purpose and FPU) are
still the same.
An architecture
From: Ingo Molnar <[EMAIL PROTECTED]>
the core syslet / async system calls infrastructure code.
Is built only if CONFIG_ASYNC_SUPPORT is enabled.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
kernel/Makefile |1
kernel/async.c |
From: Ingo Molnar <[EMAIL PROTECTED]>
Add Documentation/syslet-design.txt with a high-level description
of the syslet concepts.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
Documentation/syslet-design.txt | 137
From: Ingo Molnar <[EMAIL PROTECTED]>
add include/linux/syslet.h which contains the user-space API/ABI
declarations. Add the new header to include/linux/Kbuild as well.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
include/linux/Kbuild
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
fs/exec.c |4
include/linux/sched.h | 23
From: Ingo Molnar <[EMAIL PROTECTED]>
add include/linux/async.h which contains the kernel-side API
declarations.
it also provides NOP stubs for the !CONFIG_ASYNC_SUPPORT case.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
this is the v5 release of the syslet/threadlet subsystem:
http://redhat.com/~mingo/syslet-patches/
this release took 4 days to get out, but there were a couple of key
changes that needed some time to settle down:
- ported the code from v2.6.20 to current -git (v2.6.20-rc2 should be
On Wed, 28 Feb 2007, Ingo Molnar wrote:
> * Davide Libenzi wrote:
>
> > Did you hide all the complexity of the userspace atom decoding inside
> > another function? :)
>
> no, i made the 64-bit and 32-bit structures layout-compatible. This
> makes the 32-bit structure as large as the 64-bit
On Wed, 28 Feb 2007 18:11:11 +0900
Paul Mundt <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 22, 2007 at 12:31:20PM -0800, John Reiser wrote:
> > This patch changes arch_setup_additonal_pages() to honor vdso_enabled.
> > For i386 it also allows the option of a fixed addresss to avoid
> > fragmenting
>From originally rate-limited printk, to just printk, to current version.
Everybody had enough time to learn about vm86(2) absense.
Also remove possibility of dmesg spamming.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
arch/x86_64/ia32/ia32entry.S |4 ++--
>Quoting Thomas Gleixner <[EMAIL PROTECTED]>:
>Subject: Re: 2.6.21-rc1: known regressions (v2) (part 1)
>
>On Wed, 2007-02-28 at 23:13 +0200, Michael S. Tsirkin wrote:
>> >Subject: ThinkPad T60: no screen after suspend to RAM
>> >References : http://lkml.org/lkml/2007/2/22/391
>> >Submitter :
On Tue, 2007-02-27 at 13:54 -0500, Dale Blount wrote:
> On Fri, 2007-02-23 at 12:00 -0500, Dale Blount wrote:
> > Hi,
> >
> > Excuse me if this has been covered or fixed, I couldn't find anything in
> > the archives.
> >
> > I upgraded from 2.6.11.7 to 2.6.20.1 today and found all the drives
> >
Hi!
> > Well I had an idea after looking at k8temp -- why not make it default to
> > doing only reads from the sensor? You'd only get information from whatever
> > core/sensor combination that ACPI had last used, but it would be safe.
>
> ACPI is broken here, not k8temp, so let's fix ACPI
On Wed, Feb 28, 2007 at 05:28:27AM -0700, Eric W. Biederman wrote:
>
> What are the rules that are supposed to govern backports to stable
> trees these days anyway?
Documentation/stable_kernel_rules.txt
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Wed, 2007-02-28 at 16:53 +, James Simmons wrote:
> > On Thu, 2007-02-22 at 00:53 +, James Simmons wrote:
> > > > > +/* image data is MSB-first, fb structure is MSB-first too */
> > > > > +static inline u32 expand_color(u32 c)
> > > > > +{
> > > > > + return ((c & 1) | ((c & 2) << 7)
* Davide Libenzi wrote:
> On Wed, 28 Feb 2007, Ingo Molnar wrote:
>
> >
> > * Davide Libenzi wrote:
> >
> > > My point is, the syslet infrastructure is expensive for the kernel in
> > > terms of compat, [...]
> >
> > it is not. Today i've implemented 64-bit syslets on x86_64 and
> >
On Wed, Feb 28, 2007 at 10:13:24PM +0100, Michael Hanselmann wrote:
> On Wed, Feb 28, 2007 at 12:36:25PM -0500, Dave Jones wrote:
> > +#ifdef __powerpc__
>
> Is __powerpc__ defined when cross compiling? I'd rather use
> CONFIG_PMAC_BACKLIGHT instead of it.
Sounds ok to me.
It is true that debug registers are inherited by fork and clone.
I am 99% sure that this was never specifically intended, but it
has been this way for a long time (since 2.4 at least). It's an
implicit consequence of the do_fork implementation style, which
does a blind copy of the whole
On Wed, 2007-02-28 at 23:13 +0200, Michael S. Tsirkin wrote:
> >Subject: ThinkPad T60: no screen after suspend to RAM
> >References : http://lkml.org/lkml/2007/2/22/391
> >Submitter : Michael S. Tsirkin <[EMAIL PROTECTED]>
> >Handled-By : Ingo Molnar <[EMAIL PROTECTED]>
> >Status :
On Mon, 26 Feb 2007, Guennadi Liakhovetski wrote:
> With a post 2.6.20 kernel from powerpc.git I cannot suspend at all:
>
> pata_sil680 :00:0c.0: suspend
> ata1: suspend failed, device 0 still active
> pci_device_suspend(): ata_pci_device_suspend+0x0/0x74() returns -16
> suspend_device():
Hi!
> > OK, thanks.
> >
> > We can (I think) do pretty much the same with some additional complications
> > in worker_thread() (check !cpu_online() after try_to_freeze() and break).
>
> Okay, but I've just finished the patch that removes the freezability of
> workqueues (appended), so can we
On Wed, Feb 28, 2007 at 12:36:25PM -0500, Dave Jones wrote:
> +#ifdef __powerpc__
Is __powerpc__ defined when cross compiling? I'd rather use
CONFIG_PMAC_BACKLIGHT instead of it.
Greets,
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
>Subject: ThinkPad T60: no screen after suspend to RAM
>References : http://lkml.org/lkml/2007/2/22/391
>Submitter : Michael S. Tsirkin <[EMAIL PROTECTED]>
>Handled-By : Ingo Molnar <[EMAIL PROTECTED]>
>Status : unknown
Just reproduced this in -rc2.
Another thing I noticed:
with 2.6.20,
On Wed, 28 Feb 2007, Ingo Molnar wrote:
>
> * Davide Libenzi wrote:
>
> > My point is, the syslet infrastructure is expensive for the kernel in
> > terms of compat, [...]
>
> it is not. Today i've implemented 64-bit syslets on x86_64 and
> 32-bit-on-64-bit compat syslets. Both the 64-bit
Miklos Szeredi wrote:
What happens if the application overwrites what it had written some
time later? Nothing. The page is already read-write, the pte dirty,
so even though the file was clearly modified, there's absolutely no
way in which this can be used to force an update to the timestamp.
On Wed, 28 Feb 2007, Jan Beulich wrote:
> A change early last year reordered struct page so that ptl overlaps not only
> private, but also mapping. Since spinlock_t can be much larger, I'm wondering
> whether there's a reason to not also overlay the space index and lru take -
> are these used for
worker_thread() doesn't need to "Block and flush all signals", this was already
done by its caller, kthread().
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- 6.20-rc6-mm3/kernel/workqueue.c~signals 2007-02-20 02:21:11.0
+0300
+++ 6.20-rc6-mm3/kernel/workqueue.c 2007-02-28
On Wed, 2007-02-28 at 09:32 +0100, Ingo Molnar wrote:
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> > >> +#ifdef CONFIG_PARAVIRT
> > >> +/* After pte_t, etc, have been defined */
> > >> +#include
> > >> +#endif
> > >>
> > >
> > > hm - there's already a CONFIG_PARAVIRT conditional
> What happens if the application overwrites what it had written some
> time later? Nothing. The page is already read-write, the pte dirty,
> so even though the file was clearly modified, there's absolutely no
> way in which this can be used to force an update to the timestamp.
Which, I realize
On Feb 28, 2007, at 2:43 PM, Timur Tabi wrote:
What about major number 205? It also has the screwed-up /dev/
ttyCPM entries, but it has more room, and the CPM driver doesn't
actually use it. At least, I can't see where it uses it.
Please, let's just leave the four we have and let
the
On Wed, 2007-02-28 at 21:39 +0200, Artem Bityutskiy wrote:
> On Wed, 2007-02-28 at 19:13 +, Richard Purdie wrote:
> > +/* gives us jffs2_subsys */
> > +static decl_subsys(jffs2, NULL, NULL);
>
> There is actually a file-system subsys - look up for fs_subsys. It is
> declared at
Gentlemen,
I instrumented 2.6.21-rc1 base/power/resume.c device_resume() with
TRACE_RESUME(0) as the last statement in the function. Sure enough it
was the last hash value in the RTC after a hard reboot when resume failed:
[ 12.028820] hash matches drivers/base/power/resume.c:104
The
Commit 908b637fe793165b6aecdc875cdca67c4959a1ad removed ETH_DMA_ALIGN
but missed a usage of it in a macro, which broke the build.
Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
diff --git a/drivers/net/mv643xx_eth.h b/drivers/net/mv643xx_eth.h
index 7cb0a41..7d4e90c 100644
---
On Wed, Feb 28, 2007 at 09:27:09AM -0500, Chuck Ebbert wrote:
> Can we just put a canary in the threadinfo and check it on every
> task switch? What are the drawbacks?
Likely already too late then -- if critical state is overwritten
you crashed before. Also a lot of stack intensive codes
On Monday 26 February 2007 12:54 am, Sarah Bailey wrote:
> On Sun, Feb 25, 2007 at 08:53:03AM -0800, David Brownell wrote:
> > On Sunday 25 February 2007 12:57 am, Sarah Bailey wrote:
> > > I haven't seen any evidence that the kernel-side aio is substantially
> > > more efficient than the GNU libc
On Wed, 2007-02-28 at 12:14 +1100, Nigel Cunningham wrote:
> Controversy is no reason to give in! Nevertheless, I think you're right
> - I believe the XFS guys said they fixed the issue that had caused I/O
> to be submitted post-freeze. Well, we'll see if it appears again, won't
> we?
I get to
> >> While these entry points do not actually modify the file itself,
> >> as was pointed out, they are handy points at which the kernel gains
> >> control and could actually notice that the contents of the file are
> >> no longer the same as they were, ie. modified.
> >>
> >> From the operating
On 02/28, Rafael J. Wysocki wrote:
>
> Okay, but I've just finished the patch that removes the freezability of
> workqueues (appended), so can we please do this in a separate one?
Please, please, no. This patch is of course correct, but it breaks _a lot_
of patches in -mm tree.
May I ask you to
Patrick McHardy wrote:
> Thanks, the previous approach doesn't seem to work properly without
> unpleasant event cache hacks. This patch takes a simpler approach
> and keeps the unconfirmed list iteration, but makes sure to make
> forward progress.
>
>
>
>
On 02/28, Rafael J. Wysocki wrote:
>
> Okay, I have added a comment to freezer.h. Please have a look.
>
>
> -extern void thaw_some_processes(int all);
> +/*
> + * The PF_FREEZER_SKIP flag should be set by a vfork parent right before it
> + * calls wait_for_completion() and reset right after it
* Davide Libenzi wrote:
> My point is, the syslet infrastructure is expensive for the kernel in
> terms of compat, [...]
it is not. Today i've implemented 64-bit syslets on x86_64 and
32-bit-on-64-bit compat syslets. Both the 64-bit and the 32-bit syslet
(and threadlet) binaries work just
On Sun, 25 Feb 2007, Oleg Nesterov wrote:
> page_lock_anon_vma() uses spin_lock() to block RCU. This doesn't work with
> PREEMPT_RCU, we have to do rcu_read_lock() explicitely. Otherwise, it is
> theoretically possible that slab returns anon_vma's memory to the system
> before we do
Two fixes to arch/i386/Makefile.cpu:
1) When X86_GENERIC=y is set, use -mtune=i686 if $(CC) doesn't
support -mtune=generic. GCC 4.1.2 and earlier don't support
-mtune=generic. When building a generic kernel for a distro
that runs on i586 and better, it is nice to use
-march=i586
On Wednesday, 28 February 2007 21:08, Oleg Nesterov wrote:
> On 02/28, Rafael J. Wysocki wrote:
> >
> > On Wednesday, 28 February 2007 20:32, Oleg Nesterov wrote:
> > >
> > > I am sorry, I lost track of this problem. As for 2.6.21,
> > > create_freezeable_workqueue
> > > doesn't work and
can be downloaded from:
http://libhugetlbfs.ozlabs.org/snapshots/libhugetlbfs-dev-20070228.tar.gz
I have collected the following information:
bc56bba8f31bd99f350a5ebfd43d50f411b620c7 is first bad commit
commit bc56bba8f31bd99f350a5ebfd43d50f411b620c7
Author: Eric W. Biederman <[EMAIL PROTEC
Ingo Molnar wrote:
>> Yes, but it happens after asm/paravirt.h has already included some
>> things, and it ends up causing problems. paravirt.h still defines
>> various stub functions in the !CONFIG_PARAVIRT case, so it needs to do
>> the includes either way.
>>
>
> hm, it then needs to
Ingo Molnar wrote:
> fair enough. Please rename it to FIX_PARAVIRT_BOOTUP - you can still
> rely on it being available later on too, but we'd like to give everyone
> the right fundamental idea about this: it's meant to be a limited,
> inflexible interface for bootstrap only.
>
Will do.
On 02/28, Rafael J. Wysocki wrote:
>
> On Wednesday, 28 February 2007 20:32, Oleg Nesterov wrote:
> >
> > I am sorry, I lost track of this problem. As for 2.6.21,
> > create_freezeable_workqueue
> > doesn't work and conflict with suspend. Why can't we remove it from XFS as
> > you
> > suggested
Miklos Szeredi wrote:
While these entry points do not actually modify the file itself,
as was pointed out, they are handy points at which the kernel gains
control and could actually notice that the contents of the file are
no longer the same as they were, ie. modified.
From the operating
Add a missing #define for the platform_kernel_launch_event.
Without this fix, a call to platform_kernel_launch_event()
becomes a noop on generic kernels. SN systems require this
fix to successfully kdump/kexec from certain hardware errors.
Signed-off-by: John Keller <[EMAIL PROTECTED]>
---
On Wed, 2007-02-28 at 19:13 +, Richard Purdie wrote:
> The following patch series adds LZO compression support to the kernel
> and exposes it in a variety of places (jffs2, crypto).
>
> This is particularly useful for jffs2 where significant boot time
> speedups (~10%) and file read speed
Another option is to use 46..49 for UARTs #0..3,
and 192..195 for UARTs #4..7.
Or, perhaps better, use 46..49 for #0..3, and
192..199 for #0..7, handling the duplication in
the driver; and deprecate the old range.
That sounds like more hassle than it's worth. The discontinuous range
may be
Kumar Gala wrote:
Eh, I'm not crazy about that. That means that I have to complicate my
driver because someone else screwed up a long time ago.
If not you someone else. The cost in the driver is small compared to
fixing up all the distro's and such. If you don't provide this change
On Wed, 28 Feb 2007, Chris Friesen wrote:
> Davide Libenzi wrote:
>
> > struct async_syscall {
> > unsigned long nr_sysc;
> > unsigned long params[8];
> > long *result;
> > };
> >
> > And what would async_wait() return bak? Pointers to "struct async_syscall"
> > or pointers to
Hi Richard,
On Wed, 2007-02-28 at 19:13 +, Richard Purdie wrote:
> +/* gives us jffs2_subsys */
> +static decl_subsys(jffs2, NULL, NULL);
There is actually a file-system subsys - look up for fs_subsys. It is
declared at fs/namespace.c.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
-
On Wednesday, 28 February 2007 20:32, Oleg Nesterov wrote:
> On 02/28, Rafael J. Wysocki wrote:
> >
> > > --- workqueue.c.org 2007-02-28 18:32:48.0 +0530
> > > +++ workqueue.c 2007-02-28 18:44:23.0 +0530
> > > @@ -718,6 +718,8 @@ static void cleanup_workqueue_thread(str
> >
Add LZO1X compression support to the crypto interface, including
a couple of tests.
Also convert test_deflate into a more generic test_compress() and
avoid duplicating the data for compression and decompression tests
since this can always work both ways in the compression case.
Signed-off-by:
Allow selection of the compression mode for jffs2 via a sysfs
attribute. This establishes a sysfs presence for jffs2 through
which other compression options could easily be exported too.
Signed-off-by: Richard Purdie <[EMAIL PROTECTED]>
---
fs/jffs2/compr.c | 131
Add a "favourlzo" compression mode to jffs2 which tries to
optimise by size but gives lzo an advantage when comparing sizes.
This means the faster lzo algorithm can be preferred when there
isn't much difference in compressed size (the exact threshold can
be changed).
Signed-off-by: Richard
Add LZO1X compression/decompression support to jffs2.
LZO's interface doesn't entirely match that required by jffs2 so a
buffer and memcpy is unavoidable.
Signed-off-by: Richard Purdie <[EMAIL PROTECTED]>
---
fs/Kconfig| 10
fs/jffs2/Makefile |1
fs/jffs2/compr.c
Add LZO1X compression/decompression support to the kernel.
This is based on the standard userspace lzo library, particularly
minilzo with the headers much trimmed down and simplified for kernel
use. Its structured so that it should still diff with the userspace
version for ease of future
The following patch series adds LZO compression support to the kernel
and exposes it in a variety of places (jffs2, crypto).
This is particularly useful for jffs2 where significant boot time
speedups (~10%) and file read speed improvements (~40%) are seen when
its used with only a slight drop in
On Wednesday, 28 February 2007 12:00, Oleg Nesterov wrote:
> On 02/28, Rafael J. Wysocki wrote:
> >
> > On Wednesday, 28 February 2007 02:23, Srivatsa Vaddagiri wrote:
> > > On Wed, Feb 28, 2007 at 12:53:14AM +0300, Oleg Nesterov wrote:
> > > > I think it is good. Srivatsa?
> > >
> > > Maybe
On Feb 28, 2007, at 1:30 PM, Timur Tabi wrote:
H. Peter Anvin wrote:
Kumar Gala wrote:
Why don't we allocate the 2nd group of four as well, just at a
new location. They'll be discontinuous, but at least we'll have
support for all 8.
Right, it means two tty driver structures, but
On 02/28, Rafael J. Wysocki wrote:
>
> > --- workqueue.c.org 2007-02-28 18:32:48.0 +0530
> > +++ workqueue.c 2007-02-28 18:44:23.0 +0530
> > @@ -718,6 +718,8 @@ static void cleanup_workqueue_thread(str
> > insert_wq_barrier(cwq, , 1);
> >
H. Peter Anvin wrote:
Kumar Gala wrote:
Why don't we allocate the 2nd group of four as well, just at a new
location. They'll be discontinuous, but at least we'll have support
for all 8.
Right, it means two tty driver structures, but that's not a problem.
Eh, I'm not crazy about that.
Segher Boessenkool wrote:
Just allocate the four slots and we'll deal with
anything above this in custom products.
Another option is to use 46..49 for UARTs #0..3,
and 192..195 for UARTs #4..7.
Or, perhaps better, use 46..49 for #0..3, and
192..199 for #0..7, handling the duplication in
the
Just allocate the four slots and we'll deal with
anything above this in custom products.
Another option is to use 46..49 for UARTs #0..3,
and 192..195 for UARTs #4..7.
Or, perhaps better, use 46..49 for #0..3, and
192..199 for #0..7, handling the duplication in
the driver; and deprecate the
Fix __init declarations in Compaq SMART2 Controller driver.
Resolves MODPOST warnings similar to:
WARNING: drivers/block/cpqarray.o - Section mismatch: reference to
.init.text:cpqarray_init_one from .data.rel.local between 'cpqarray_pci_driver'
(at offset 0x20) and 'smart1_access'
On Wed, 28 Feb 2007, Eric Dumazet wrote:
> On Wednesday 28 February 2007 19:37, Davide Libenzi wrote:
>
> > + list_del(>rdllink);
> > + if (!(epi->event.events & EPOLLET) && (revents &
> > epi->event.events))
> > + list_add_tail(>rdllink, );
> > +
Chuck Ebbert wrote:
> There are two patches for raid5/6 out there that might fix this. I'll
> attach them (the second just fixes a minor bug in the first one.)
Never mind, those patches are already in 2.6.21-rc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Kumar Gala wrote:
Why don't we allocate the 2nd group of four as well, just at a new
location. They'll be discontinuous, but at least we'll have support for
all 8.
Right, it means two tty driver structures, but that's not a problem.
-hpa
-
To unsubscribe from this list: send the
Dan Malek wrote:
Just allocate the four slots and we'll deal with
anything above this in custom products.
Assuming that this is the agreed-upon standard, should I arbitrarily restrict my driver to
4 ports, or allow all 8?
I assume that if a driver already claims a particular major/minor
On Feb 28, 2007, at 12:20 PM, Dan Malek wrote:
On Feb 28, 2007, at 1:00 PM, H. Peter Anvin wrote:
I would much rather see these devices moved to a different minor
range.
No. We just did that all too recently, and
i don't know why the minors didn't get
allocated properly. I don't want to
On Wednesday, 28 February 2007 14:17, Srivatsa Vaddagiri wrote:
> On Wed, Feb 28, 2007 at 12:11:03PM +0100, Rafael J. Wysocki wrote:
> > > In addition to thawing worker thread before kthread_stopping it, there
> > > are minor changes required in worker threads, to check for
> > >
On Wednesday 28 February 2007 19:37, Davide Libenzi wrote:
> + list_del(>rdllink);
> + if (!(epi->event.events & EPOLLET) && (revents &
> epi->event.events))
> + list_add_tail(>rdllink, );
> + else {
Is the ( ... & epi->event.events)
(Resending to wider audience)
__init to __cpuinit in mtrr code.
Resolves warnings similar to:
WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from
.text between 'identify_cpu' (at offset 0xc040b38e) and 'detect_ht'
Signed-off-by: Prarit Bhargava <[EMAIL PROTECTED]>
If a process is closing /dev/input/mice and an mouse disconnects simulta-
neously, the system is likely to oops. This usually happens when someone
hits F1 or logs out from X, and flips a KVM while the system
is reacting.
I reproduced the issue by running this:
while true; do cat
Davide Libenzi wrote:
struct async_syscall {
unsigned long nr_sysc;
unsigned long params[8];
long *result;
};
And what would async_wait() return bak? Pointers to "struct async_syscall"
or pointers to "result"?
Either one has downsides. Pointer to struct async_syscall
On Wed, 2007-02-28 at 10:51 -0800, Jean Tourrilhes wrote:
> That's why I always specify the kernel version. I'll look into
> that, I'm sure it's not the end of the world ;-)
Sure, just wanted to point it out.
> In which sense ? Wireless interface are regular netdevices.
Yeah but in
On Wed, Feb 28, 2007 at 11:23:46AM +0100, Gerd Hoffmann wrote:
> The test which automatically enables the backup timer on some HP
> machines doesn't trigger on other hardware which needs the backup
> timer too.
Did you figure out *why* that test doesn't trigger?
Making that work seems a better
On Wed, Feb 28, 2007 at 10:16:05AM +0100, Johannes Berg wrote:
> Hi,
>
> > Patch for 2.6.20 is attached.
>
> ... and in the meantime netdevices aren't class_device any more :) IOW,
> your patch isn't going to work any more.
That's why I always specify the kernel version. I'll look
On Wed, Feb 28, 2007 at 08:05:16PM +0300, Dmitriy Monakhov wrote:
> - ecryptfs_write_inode_size_to_metadata() error code was ignored.
> - i_op->setxattr() must be supported by lower fs because used below.
>
> Signed-off-by: Monakhov Dmitriy <[EMAIL PROTECTED]>
Acked-by: Michael Halcrow
Dan Williams wrote:
> I can reliably reproduce a null pointer dereference on 2.6.20 and
> 2.6.21-rc2. I will keep digging to find the kernel version where this
> last worked, but wanted to see if there were any immediate experiments I
> should try.
>
> The failure is caused by running tiobench
On Wed, 28 Feb 2007, Linus Torvalds wrote:
> On Wed, 28 Feb 2007, Davide Libenzi wrote:
> >
> > Here we very much agree. The way I'd like it:
> >
> > struct async_syscall {
> > unsigned long nr_sysc;
> > unsigned long params[8];
> > long result;
> > };
>
> No, the "result" needs to
On Wed, Feb 28, 2007 at 10:34:37AM +0100, Jarek Poplawski wrote:
> On 28-02-2007 02:27, Jean Tourrilhes wrote:
> > Hi all,
> ...
> > Patch for 2.6.20 is attached. The patch was tested on a system
> > running the hotplug scripts, and on another system running udev.
> >
> > Have fun...
On Wed, 28 Feb 2007, Davide Libenzi wrote:
>
> Here we very much agree. The way I'd like it:
>
> struct async_syscall {
> unsigned long nr_sysc;
> unsigned long params[8];
> long result;
> };
No, the "result" needs to go somewhere else. The caller may be totally
On Wed, Feb 28, 2007 at 07:36:17AM -0800, Greg KH wrote:
> On Tue, Feb 27, 2007 at 05:27:41PM -0800, Jean Tourrilhes wrote:
> > diff -u -p linux/drivers/base/class.j1.c linux/drivers/base/class.c
> > --- linux/drivers/base/class.j1.c 2007-02-26 18:38:10.0 -0800
> > +++
On Wednesday, 28 February 2007 19:17, Gautham R Shenoy wrote:
> On Wed, Feb 28, 2007 at 08:37:26AM +0530, Srivatsa Vaddagiri wrote:
> >
> > Hmm ..good point. So can we assume that disable/enable_nonboot_cpus() are
> > called
> > with processes frozen already?
> >
> > Gautham, you need to take
101 - 200 of 728 matches
Mail list logo
