Current git-x86 seems to be totally broken on i386
commit a6f08929f0566f9d309ef5f6651371d8e20fc833
Author: Russell Leidich [EMAIL PROTECTED]
Date: Wed Jan 2 22:46:22 2008 +0100
x86: AMD Thermal Interrupt Support
-- after you got it to compile with
Signed-off-by: Andi Kleen [EMAIL
On Wednesday, 2 January 2008 21:35:03 Matthias Schniedermeyer wrote:
Hi
Currently i'm deleting about 500.000 files on a XFS-filesystem which
takes a few minutes, as i had a top open i saw that 'wa' is shown as
0.0% (Nothing else running currently) and everything except 'id' is near
the
Allen Martin wrote:
The software definitely provides that guarantee for all NCQ-capable
controllers.
Well if that's not it, it must be some problem entering ADMA legacy
mode. Here's what the Windows driver does:
ADMACtrl.aGO = 0
ADMACtrl.aEIEN = 0
poll {
until ADMAStatus.aLGCY = 1 ||
On Fri, 28 Dec 2007 13:26:07 -0800 (PST) Jonathan Lim [EMAIL PROTECTED] wrote:
It's possible that the values used in and returned from jiffies_to_usecs() are
incorrect because of truncation when variables of type u64 are involved. So a
function specific to that type is used instead.
Diff'd
Linda Walsh wrote:
Alan Cox wrote:
rate began falling; at 128k block-reads-at-a-time or larger, it drops
below
20MB/s (only on buffered SATA).
Try disabling NCQ - see if you've got a drive with the 'NCQ = no
readahead' flaw.
---
I'm not aware, off hand, how to disable NCQ. I haven't had
Tejun Heo wrote:
Robert Hancock wrote:
Jeff Garzik wrote:
Tejun Heo wrote:
Thanks a lot for the detailed explanation. Nvidia ppl, any ideas?
FLUSH is used regularly. We really need to fix this.
I reiterate my opinion :) ... We should remove ADMA support from
sata_nv. It's only in a
Andrew Morton wrote:
On Fri, 28 Dec 2007 13:26:07 -0800 (PST) Jonathan Lim [EMAIL PROTECTED] wrote:
It's possible that the values used in and returned from jiffies_to_usecs() are
incorrect because of truncation when variables of type u64 are involved. So a
function specific to that type is
Carlos Corbacho wrote:
(CC'ing linux-input, as that is the relevant subsystem list for wistron-btns).
Rémi Hérilier wrote:
To use my previous patch (wistron_btns support for fujitsu-siemens amilo
pro edition v3505) with my laptop, I need to make the wistron module
compile for x86_64. It is
Bartlomiej Zolnierkiewicz wrote:
Delete filenames/versions from comments.
I'm leaving decisions about adding DRV_VERSION defines and MODULE_VERSION()-s
to maintainers of the respective drivers.
While at it:
* Remove unused VERSION define from ide.c.
* Remove unused/stale DRV_VERSION define
I can't see a reason why these shouldn't work on every group. However,
they only seem to work on named groups. This patch allows the group
functions to work on anonymous groups (those with NULL names).
Signed-off-by: James Bottomley [EMAIL PROTECTED]
---
Again, this is something that's needed
This patch is the beginning of moving the attribute_containers to use
attribute groups exclusively. The attr element is now deprecated and
will eventually be removed (along with all the hand rolled code for
doing exactly what attribute groups do) when all the consumers are
converted to attribute
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
include/asm-x86/ptrace-abi.h |2 ++
1 file changed, 2 insertions(+)
Index: linux/include/asm-x86/ptrace-abi.h
===
--- linux.orig/include/asm-x86/ptrace-abi.h
+++
According to AMD RDTSC can be synchronized through MFENCE.
Implement the necessary CPUID bit for that.
Cc: [EMAIL PROTECTED]
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/amd.c|3 +++
arch/x86/kernel/setup_64.c |4 ++--
include/asm-x86/cpufeature.h |1 +
According to Intel RDTSC can be always synchronized with LFENCE
on all current CPUs. Implement the necessary CPUID bit for that.
It is unclear yet if that is true for all future CPUs too,
but if there's another way the kernel can be always updated.
Cc: [EMAIL PROTECTED]
Signed-off-by: Andi
Moving things out of processor.h is always a good thing.
Also needed to avoid include loop in later patch.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
include/asm-x86/nops.h | 90
include/asm-x86/processor.h | 86
nsec_barrier() is a new barrier primitive that stops RDTSC speculation
to avoid races with timer interrupts on other CPUs.
Add it to all architectures. Except for x86 it is a nop right now.
I only tested x86, but it's a very simple change.
On x86 it expands either to LFENCE (for Intel CPUs) or
And replace with nsec_barrier() as needed which has the same effect
of preventing unnecessary speculation around RDTSC.
For the standard gtod() like calls the previous patch already added the
necessary barriers
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/time_64.c |4
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
include/asm-x86/cpufeature.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/include/asm-x86/cpufeature.h
===
--- linux.orig/include/asm-x86/cpufeature.h
+++
So that we don't have to implement it on 32bit.
I would actually like to remove it on 64bit too.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/Kconfig|5 +
arch/x86/kernel/cpu/mcheck/mce_64.c | 16 ++--
2 files changed, 19 insertions(+), 2
It is not really useful to lock machine checks against oopses. And
machine checks normally don't nest, so they don't need their
own locking. Just call bust_spinlock/console_verbose directly.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/mcheck/mce_64.c |3 ++-
1 file
Previously it was only run for Intel CPUs, but AMD Fam10h implements MWAIT too.
This matches 64bit behaviour.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/common.c |2 ++
arch/x86/kernel/cpu/intel.c |1 -
2 files changed, 2 insertions(+), 1 deletion(-)
Index:
Previously there was a AMD specific quirk to handle the case of
AMD Fam10h MWAIT not supporting any C states. But it turns out
that CPUID already has ways to detectly detect that without
using special quirks.
The new code simply checks if MWAIT supports at least C1 and doesn't
use it if it
Previously the code used a single timer that then used smp_call_function
to interrupt all CPUs while the original CPU was waiting for them.
But it is better / more real time and more power friendly to simply run
individual timers on each CPU so they all do this independently.
This way no
They are not time critical and delaying them a little for
the next regular wakeup is no problem.
Also when a CPU is idle then it is unlikely to generate
errors anyways, so it is ok to check only when the CPU
is actually doing something.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
.. and report them in /proc/interrupts
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/mcheck/mce_64.c |6 ++
arch/x86/kernel/irq_32.c| 10 ++
arch/x86/kernel/irq_64.c|9 +
include/asm-x86/mce.h |3 +++
Need this in the next patch in time_init and that happens early.
This includes a minor fix on i386 where early_intel_workarounds()
[which is now called early_init_intel] really executes early as
the comments say.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/amd.c|
After a lot of discussions with AMD it turns out that TSC
on Fam10h CPUs is synchronized when the CONSTANT_TSC cpuid bit is set.
Or rather that if there are ever systems where that is not
true it would be their BIOS' task to disable the bit.
So finally use TSC gettimeofday on Fam10h by default.
Trust the ACPI code to disable TSC instead when C3 is used.
AMD Fam10h does not disable TSC in any C states so the
check was incorrect there anyways after the change
to handle this like Intel on AMD too.
This allows to use the TSC when C3 is disabled in software
(acpi.max_c_state=2), but the
The ACPI code currently disables TSC use in any C2 and C3
states. But the AMD Fam10h BKDG documents that the TSC
will never stop in any C states when the CONSTANT_TSC bit is
set. Make this disabling conditional on CONSTANT_TSC
not set on AMD.
I actually think this is true on Intel too for C2
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/mm/fault_32.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/x86/mm/fault_32.c
===
--- linux.orig/arch/x86/mm/fault_32.c
+++
They now look like
hal-resmgr[13791]: segfault at 3c rip 2b9c8caec182 rsp 7fff1e825d30 error 4 in
libacl.so.1.1.0[2b9c8caea000+6000]
This makes it easier to pinpoint bugs to specific libraries.
And printing the offset into a mapping also always allows to find the
correct fault point in a
Currently pda-power adds both ac and usb power supply units.
This patch fixes it so that psu are added only if they are enabled.
Signed-off-by: Dmitry Baryshkov [EMAIL PROTECTED]
diff --git a/drivers/power/pda_power.c b/drivers/power/pda_power.c
index c058f28..42eac09 100644
---
On Wed, 2 Jan 2008 16:06:20 -0800 Pallipadi, Venkatesh [EMAIL PROTECTED]
wrote:
-Original Message-
From: Mark Lord [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 02, 2008 3:42 PM
To: Arjan van de Ven
Cc: Pallipadi, Venkatesh; Andrew Morton; [EMAIL PROTECTED];
[EMAIL
Subject: Make checkpatch.pl's quiet option not print the summary on no errors
From: Arjan van de Ven [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Right now, in quiet mode, checkpatch.pl still prints a summary line even
if the patch is 100% clean. IMO, quiet mode should mean no output if clean,
the
On Sun, 2007-12-30 at 15:28 +0100, Ingo Molnar wrote:
* Huang, Ying [EMAIL PROTECTED] wrote:
+struct efi_tables efi_tables;
+EXPORT_SYMBOL(efi_tables);
+enum bios_type bios_type = BIOS_LEGACY;
+EXPORT_SYMBOL(bios_type);
please make all the new exports EXPORT_SYMBOL_GPL().
OK, I
Subject: move WARN_ON() out of line
From: Arjan van de Ven [EMAIL PROTECTED]
CC: Ingo Molnar [EMAIL PROTECTED]
CC: Andrew Morton [EMAIL PROTECTED]
A quick grep shows that there are currently 1145 instances of WARN_ON
in the kernel. Currently, WARN_ON is pretty much entirely inlined,
which makes
Subject: Add the end-of-trace marker and the module list to WARN_ON()
From: Arjan van de Ven [EMAIL PROTECTED]
CC: Ingo Molnar [EMAIL PROTECTED]
CC: Andrew Morton [EMAIL PROTECTED]
Unlike oopses, WARN_ON() currently does't print the loaded modules list.
This makes it harder to take action on
Subject: consolidate oops end/ID printing code in panic.c
From: Arjan van de Ven [EMAIL PROTECTED]
CC: Ingo Molnar [EMAIL PROTECTED]
CC: Andrew Morton [EMAIL PROTECTED]
This patch consolidates the 2 places that print an oops end marker and ID
into a single function; this patch follows the
On Wed Jan 2 16:36:47 2008, [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
On Fri, 28 Dec 2007 13:26:07 -0800 (PST) Jonathan Lim [EMAIL PROTECTED]
wrote:
It's possible that the values used in and returned from jiffies_to_usecs()
are incorrect because of truncation when variables of
Currently the notify_page_fault helper is used to test it the page
fault was caused by a kprobe causing an early return from do_page_fault.
Change the name of the helper to is_kprobe_fault to match the usage and
remove the preempt_disable/enable pair around kprobe_running() with an
explicit test
ebizzy is designed to generate a workload resembling common web application
server workloads. It is especially useful for testing
changes to memory management, and whenever a highly threaded application
with a large working set and many vmas is needed.
This is release 0.3 of ebizzy. It reports
-Original Message-
From: Andrew Morton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 02, 2008 4:52 PM
To: Pallipadi, Venkatesh
Cc: Mark Lord; Arjan van de Ven; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Ingo Molnar; linux-kernel@vger.kernel.org;
[EMAIL PROTECTED]
Subject: Re: +
Jonathan Lim wrote:
Peter,
Would you be willing to include the u64 function as part of your patch to make
it available kernel-wide? It just needs:
u64 inline jiffies_to_usecs_u64(const u64 j)
and for the symbol to be exported. Thanks.
It should be a separate patch (new functionality
On Wed, 2008-01-02 at 13:42 -0700, Bjorn Helgaas wrote:
The patch below was put in 2.6.23.12 as a fix for
http://bugzilla.kernel.org/show_bug.cgi?id=9514. It apparently
does make 9514 go away, but only by coincidence. There are a
couple other ideas about fixing 9514. My proposed patch is
[PATCH] x86_64: not clear empty_zero_page again
empty_zero_page is in .bss section, and it is cleared in clear_bss by
x86_64_start_kernel. So don't clear that again in mem_init
Signed-off-by: Yinghai Lu [EMAIL PROTECTED]
Index: linux-2.6/arch/x86/mm/init_64.c
On Wed, Jan 02, 2008 at 05:01:02PM -0800, Harvey Harrison wrote:
Begin to unify do_page_fault(), easy code movement first.
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
---
Ingo, similar to the kprobes unification patches I did, it gets a bit
uglier before it gets better ;-)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is also the issue of compiled code which explicitly raises and
lowers capabilities around critical code sections (ie., as they were
intended to be used) is also not well served by this change.
That is, unless the code was compiled with things
This is the bug fix for
http://bugzilla.kernel.org/show_bug.cgi?id=9674
It's available here:
master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
I've just attached it below as well.
James
---
From 751bf4d7865e4ced406be93b04c7436d866d3684 Mon Sep 17 00:00:00 2001
From:
On Wed, 2 Jan 2008, James Bottomley wrote:
To say that another way:
the code is functionally equivalent, EXCEPT IT ISN'T, and it's
known to be broken.
wouldn't you say my version is more honest and correct?
No. Just because a bug appears when a particular piece of code
On Thu, 2008-01-03 at 01:56 +0100, Arjan van de Ven wrote:
Subject: move WARN_ON() out of line
From: Arjan van de Ven [EMAIL PROTECTED]
CC: Ingo Molnar [EMAIL PROTECTED]
CC: Andrew Morton [EMAIL PROTECTED]
A quick grep shows that there are currently 1145 instances of WARN_ON
in the
On Wed, 2008-01-02 at 17:09 +0100, Pavel Machek wrote:
On Wed 2008-01-02 10:03:59, Yi Yang wrote:
On Wed, 2008-01-02 at 00:20 +0100, Pavel Machek wrote:
Hi!
/proc/acpi/wakeup is also case-sensitive, case-insensitive is better.
Why?
A user uses device bus id like 'C093' to
On Thu, 2008-01-03 at 04:45 +0300, Alexey Dobriyan wrote:
On Wed, Jan 02, 2008 at 05:01:02PM -0800, Harvey Harrison wrote:
Begin to unify do_page_fault(), easy code movement first.
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
---
Ingo, similar to the kprobes unification patches I
On Wed, 2008-01-02 at 17:09 +0100, Pavel Machek wrote:
On Wed 2008-01-02 10:03:59, Yi Yang wrote:
On Wed, 2008-01-02 at 00:20 +0100, Pavel Machek wrote:
Hi!
/proc/acpi/wakeup is also case-sensitive, case-insensitive is better.
Why?
A user uses device bus id like 'C093' to
Hi Clifford,
Thanks for the report.
PowerPC problems should be reported to [EMAIL PROTECTED]
This has been fixed in the current (approaching 2.6.24) kernel. It
should be fixed in 2.6.23.xx, so I have cc'd this to
[EMAIL PROTECTED] (and linuxppc-dev, of course).
(Also, please post patches
Begin to unify do_page_fault(), easy code movement first.
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
---
Ingo, Alexey Dobriyan noticed an obvious typo CONFIG_x86_64 in
the previous version, this is a fixed patch.
arch/x86/mm/fault_32.c | 38 +-
Harvey Harrison wrote:
There is no such thing as CONFIG_x86_64 .
My apologies, testing/compiling on X86_32 here.
Please also compile for x86-64, even if you can't easily test it
(although you can always boot under qemu, even if it's slow.)
Unification patches especially.
-hpa
--
Hi Harvey,
Harvey Harrison wrote:
Currently the notify_page_fault helper is used to test it the page
fault was caused by a kprobe causing an early return from do_page_fault.
Change the name of the helper to is_kprobe_fault to match the usage and
remove the preempt_disable/enable pair around
On Thu, 3 Jan 2008 13:16:24 +1100 Stephen Rothwell [EMAIL PROTECTED] wrote:
This has been fixed in the current (approaching 2.6.24) kernel. It
should be fixed in 2.6.23.xx, so I have cc'd this to
[EMAIL PROTECTED] (and linuxppc-dev, of course).
Should have been [EMAIL PROTECTED] (where I
On Wed, 2008-01-02 at 21:36 -0500, Masami Hiramatsu wrote:
Hi Harvey,
Harvey Harrison wrote:
Currently the notify_page_fault helper is used to test it the page
fault was caused by a kprobe causing an early return from do_page_fault.
Change the name of the helper to is_kprobe_fault to
On Wed 2 Jan 2008 13:47, David Brownell pondered:
On Wednesday 02 January 2008, Robin Getz wrote:
From: Robin Getz [EMAIL PROTECTED]
Allow embedded developers to turn support for USB Hubs off even if
they have a full root hub. This saves the overhead (RAM and Flash size).
ISTR that it
Hi Linus,
Please pull from the repository at
git pull git://git.linux-nfs.org/pub/linux/nfs-2.6.git
This will update the following files through the appended changesets.
Cheers,
Trond
fs/nfs/nfs4proc.c | 34 --
fs/nfs/nfs4renewd.c
Harvey Harrison wrote:
On Wed, 2008-01-02 at 21:36 -0500, Masami Hiramatsu wrote:
Hi Harvey,
Harvey Harrison wrote:
Currently the notify_page_fault helper is used to test it the page
fault was caused by a kprobe causing an early return from do_page_fault.
Change the name of the helper to
On Jan 3, 2008 2:47 AM, David Brownell [EMAIL PROTECTED] wrote:
On Wednesday 02 January 2008, Robin Getz wrote:
From: Robin Getz [EMAIL PROTECTED]
Allow embedded developers to turn support for USB Hubs off even if they
have a
full root hub. This saves the overhead (RAM and Flash size).
On Wednesday 02 January 2008, Robin Getz wrote:
On Wed 2 Jan 2008 13:47, David Brownell pondered:
On Wednesday 02 January 2008, Robin Getz wrote:
From: Robin Getz [EMAIL PROTECTED]
Allow embedded developers to turn support for USB Hubs off even if
they have a full root hub. This
On Wednesday 02 January 2008, Alan Stern wrote:
The transaction translators in external high speed hubs require
hosts to issue particular USB transactions. If the host controller
doesn't implement the that split transaction support, then it won't
be supporting external hubs.
So in
Harvey Harrison wrote:
My apologies, testing/compiling on X86_32 here.
Do you seriously think code is getting better and more readable because
of this liberal #ifdef sprinkling in every possible direction?
Well, this of course is not the end of the road, but it makes it
obvious where the
On Jan 3, 2008 4:58 AM, Alan Stern [EMAIL PROTECTED] wrote:
On Wed, 2 Jan 2008, David Brownell wrote:
On Wednesday 02 January 2008, Alan Stern wrote:
On Wed, 2 Jan 2008, Mike Frysinger wrote:
perhaps the code size is arguable as to whether it really matters.
the reason we want it
Here's the updated patch:
Changed the real-time patch code to detect recursive calls
to dev_queue_xmit and drop the packet when detected.
Signed-off-by: Mark Beauchemin [EMAIL PROTECTED]
diff -ru linux-2.6.24-rc5-rt1/include/linux/netdevice.h
Quoting Dave Hansen ([EMAIL PROTECTED]):
One of the benefits of the r/o bind mount patches is that they
make it explicit when a write to a superblock might occur.
We currently search sb-s_files when remounting rw-ro to look
for writable files. But, that search is not comprehensive, and
it
Use a central is_kprobe_fault() inline in kprobes.h to remove all
of the arch-dependant, practically identical implementations in
avr32, ia64, powerpc, s390, sparc64, and x86.
avr32 was the only arch without the preempt_disable/enable pair
in its notify_page_fault implementation. This should be
Robert Hancock wrote:
What we're doing to enter legacy mode is essentially:
-wait until ADMA status indicates IDLE bit set (max wait of 1 microsecond)
-clear GO bit in control register
-wait until status indicates LEGACY bit set (max wait of 1 microsecond)
and to enter ADMA mode:
-set GO bit
On Thu, Jan 03, 2008 at 09:29:42AM +0530, Dhaval Giani wrote:
On Wed, Jan 02, 2008 at 01:54:12PM -0800, Christoph Lameter wrote:
Just traced it again on my system: It is okay for the number of pages on
the quicklist to reach the high count that we see (although the 16 bit
limits are
Robert Hancock wrote:
..
From some of the traces I took previously (posted on LKML as sata_nv
ADMA controller lockup investigation way back in Feb 07), what seems to
occur is that when the second command is issued very rapidly (within
less than 20 microseconds, or potentially longer) after
Pallipadi, Venkatesh wrote:
-Original Message-
From: Mark Lord [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 02, 2008 3:42 PM
To: Arjan van de Ven
Cc: Pallipadi, Venkatesh; Andrew Morton; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Ingo Molnar; linux-kernel@vger.kernel.org;
[EMAIL
Pallipadi, Venkatesh wrote:
-Original Message-
From: Andrew Morton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 02, 2008 4:52 PM
To: Pallipadi, Venkatesh
Cc: Mark Lord; Arjan van de Ven; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Ingo Molnar; linux-kernel@vger.kernel.org;
[EMAIL
Robert Hancock wrote:
Linda Walsh wrote:
Alan Cox wrote:
rate began falling; at 128k block-reads-at-a-time or larger, it
drops below
20MB/s (only on buffered SATA).
Try disabling NCQ - see if you've got a drive with the 'NCQ = no
readahead' flaw.
http://linux-ata.org/faq.html#ncq
---
On Wed, Jan 02, 2008 at 01:54:12PM -0800, Christoph Lameter wrote:
Just traced it again on my system: It is okay for the number of pages on
the quicklist to reach the high count that we see (although the 16 bit
limits are weird. You have around 4GB of memory in the system?). Up to
1/16th of
Hi Wang.
You a heads up. I will most likely apply
the remaining of the patches tonight, except the UM stuff
which I hope Jeff to take and the final removal of TOPDIR
may wait a bit.
I want the s390, xfs and um changes to hit -mm at least
and we have several external modules that uses TOPDIR.
On Jan 3, 2008 11:43 AM, David Brownell [EMAIL PROTECTED] wrote:
On Wednesday 02 January 2008, Robin Getz wrote:
On Wed 2 Jan 2008 13:47, David Brownell pondered:
On Wednesday 02 January 2008, Robin Getz wrote:
From: Robin Getz [EMAIL PROTECTED]
Allow embedded developers to turn
On Thu, Jan 03, 2008 at 01:56:58AM +0100, Arjan van de Ven wrote:
Subject: move WARN_ON() out of line
From: Arjan van de Ven [EMAIL PROTECTED]
CC: Ingo Molnar [EMAIL PROTECTED]
CC: Andrew Morton [EMAIL PROTECTED]
A quick grep shows that there are currently 1145 instances of WARN_ON
in the
Hi Harvey,
Thank you for greate work!
This seems including all of what I've expected.
I'll try to test.
Please send this to all of kprobe maintainers, Because this
involves all of the architectures which kprobes supports.
Maintainers;
could you help reviewing this?
Thank you,
Best Regards,
Mark Lord wrote:
Robert Hancock wrote:
..
From some of the traces I took previously (posted on LKML as sata_nv
ADMA controller lockup investigation way back in Feb 07), what seems
to occur is that when the second command is issued very rapidly
(within less than 20 microseconds, or
On Jan 2, 2008 10:57 PM, J. Bruce Fields [EMAIL PROTECTED] wrote:
On Thu, Jan 03, 2008 at 08:51:54AM +1100, Herbert Xu wrote:
On Wed, Jan 02, 2008 at 07:29:59PM +0100, Torsten Kaiser wrote:
Vanilla 2.6.24-rc6 seems stable. I did not see any crash or warnings.
OK that's great. The
Convert semaphore to mutex in struct class.
All the patches in this series should be applyed simultaneously
toc:
---
1-driver-core-struct-class-convert-semaphore-to-mutex.patch
2-i2c-struct-class-convert-semaphore-to-mutex.patch
3-ieee1394-struct-class-convert-semaphore-to-mutex.patch
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/base/class.c | 22 +++---
drivers/base/core.c| 13 ++---
include/linux/device.h |3 ++-
3 files changed, 19 insertions(+), 19 deletions(-)
diff -upr
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/i2c/i2c-core.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff -upr linux/drivers/i2c/i2c-core.c linux.new/drivers/i2c/i2c-core.c
--- linux/drivers/i2c/i2c-core.c
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/ieee1394/nodemgr.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff -upr linux/drivers/ieee1394/nodemgr.c
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/power/apm_power.c |6 +++---
drivers/power/power_supply_core.c |8
2 files changed, 7 insertions(+), 7 deletions(-)
diff -upr linux/drivers/power/apm_power.c
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/rtc/interface.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -upr linux/drivers/rtc/interface.c linux.new/drivers/rtc/interface.c
--- linux/drivers/rtc/interface.c
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/scsi/hosts.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -upr linux/drivers/scsi/hosts.c linux.new/drivers/scsi/hosts.c
--- linux/drivers/scsi/hosts.c 2007-12-28
Signed-off-by: Erez Zadok [EMAIL PROTECTED]
---
fs/unionfs/debug.c | 50 ++
1 files changed, 26 insertions(+), 24 deletions(-)
diff --git a/fs/unionfs/debug.c b/fs/unionfs/debug.c
index c2b8b58..5f1d887 100644
--- a/fs/unionfs/debug.c
+++
The following is a series of patchsets related to Unionfs. This is the
third set of patchsets resulting from an lkml review of the entire unionfs
code base. The most significant change here is a locking/race bugfix during
dentry revalidation.
These patches were tested (where appropriate) on
Lock parent dentries during revalidation.
Reduce total number of lockdep classes used.
Signed-off-by: Erez Zadok [EMAIL PROTECTED]
---
fs/unionfs/dentry.c | 13 -
fs/unionfs/fanout.h |3 ++-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/fs/unionfs/dentry.c
Signed-off-by: Erez Zadok [EMAIL PROTECTED]
---
fs/unionfs/unlink.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/unionfs/unlink.c b/fs/unionfs/unlink.c
index a1c82b6..1e370a1 100644
--- a/fs/unionfs/unlink.c
+++ b/fs/unionfs/unlink.c
@@ -79,7 +79,7 @@ static int
Use mutex instead of semaphore in struct class.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
drivers/spi/spi.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -upr linux/drivers/spi/spi.c linux.new/drivers/spi/spi.c
--- linux/drivers/spi/spi.c 2007-12-28
On Thursday 03 January 2008 10:35, Mike Travis wrote:
Hi Nick,
Have you done anything more with allowing 256 CPUS in this spinlock
patch? We've been testing with 1k cpus and to verify with -mm kernel,
we need to unpatch these spinlock changes.
Thanks,
Mike
Hi Mike,
Actually I had it in
On Jan 2, 2008 7:14 PM, Stefan Richter [EMAIL PROTECTED] wrote:
Dave Young wrote:
On Dec 29, 2007 7:42 PM, Stefan Richter [EMAIL PROTECTED] wrote:
However, Dave's postings lack a References: header which refer to his
00/12 posting.
[To let mail readers show it as a thread.]
(Also, a
From: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
This patch adds CONFIG_HAVE_KRETPROBES to the arch/arch/Kconfig file
for relevant architectures with kprobes support. This facilitates easy
handling of in-kernel modules (like samples/kprobes/kretprobe_example.c)
that depend on kretprobes being
On Thu, 2008-01-03 at 00:57 -0500, Erez Zadok wrote:
diff --git a/fs/unionfs/debug.c b/fs/unionfs/debug.c
index c2b8b58..5f1d887 100644
--- a/fs/unionfs/debug.c
+++ b/fs/unionfs/debug.c
void __show_inode_times(const struct inode *inode,
@@ -472,15 +473,15 @@ void __show_inode_times(const
PCI Express ASPM defines a protocol for PCI Express components in the D0
state to reduce Link power by placing their Links into a low power state
and instructing the other end of the Link to do likewise. This
capability allows hardware-autonomous, dynamic Link power reduction
beyond what is
301 - 400 of 855 matches
Mail list logo
