On Wed 2 Jan 2008 22:43, David Brownell pondered:
> This patch might be improved slightly -- in ways that, as I
> understand things, could save some RAM on Blackfin! -- by
> having the BLACKLIST_HUB option get rid of the transaction
> translator support (changing C code not just Kconfig).
> It's pr
On Thu, Jan 03, 2008 at 03:21:36PM +0800, Dave Young wrote:
...
> I don't know if there's other possible warning places with this mutex
> or not, if you have any ideas about this, please tell me.
I think lockdep is just to tell such things. So, the question is, how
much it was tested already, bec
On Wednesday 02 January 2008, Bryan Wu wrote:
> B.T.W, 2 questions about the MUSB driver:
> 1. What's the plan for mainline merge of the whole MUSB driver? maybe
> I can cleanup current Blackfin ports to you guys.
It might as well merge in 2.6.25-early. It'll be easier to integrate
patches that w
The trace output is very verbose with outputing both the
IP address (Instruction Pointer not Internet Protocol!)
and the kallsyms symbol. So if kallsyms is configured into
the kernel, another file is created in the debugfs system.
This is the trace_symonly file that leaves out the IP address.
Here
Add "notrace" annotation to x86_64 specific files.
Signed-off-by: Arnaldo Carvalho de Melo <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86/kernel/head64.c |2 +-
arch/x86/kernel/nmi_64.c |2 +-
arch/x86/kernel/setup64.c |4 ++--
arch/x8
MCOUNT will disable the regparm parameters of the i386 compile
options. When doing so, this breaks the prototype of do_IRQ
where the fastcall must be explicitly called.
Also fixed some whitespace damage in the call to do_IRQ.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86/kernel/
This patch adds an interface into debugfs.
/debugfs/mctracer/ctrl
echoing 1 into the ctrl file turns on the tracer,
and echoing 0 turns it off.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
lib/mcount/tracer.c | 87 +++-
lib/mcount/tra
This adds the task comm and pid to the trace output. This gives the
output like:
CPU 0: sshd:2605 [] remove_wait_queue+0xc/0x4a <--
[] free_poll_entry+0x1e/0x2a
CPU 2: bash:2610 [] tty_check_change+0x9/0xb6 <--
[] tty_ioctl+0x59f/0xcdd
CPU 0: sshd:2605 [] _spin_lock_irqsave+0xe/0x81 <--
[] remo
Add the notrace annotations to some of the vsyscall functions.
Note: checkpatch errors on the define of vsyscall_fn because it thinks
that it is a complex macro that needs paranthesis. Unfortunately
we can't put paranthesis on this macro.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
--
If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
non-zero value the mcount routine will be called everytime we enter a kernel
function that is not marked with the "notrace" attribute.
The mcount routine will then call a registered function if a function
happens to be re
>From patch-2.6.21.5-rt20. Annotates functions that should not be profiler
instrumented, i.e. where mcount should not be called at function entry.
Signed-off-by: Arnaldo Carvalho de Melo <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
arch/x86/kernel/apic_32.c |2 +-
Mark with "notrace" functions in core code that should not be
traced. The "notrace" attribute will prevent gcc from adding
a call to mcount on the annotated funtions.
Signed-off-by: Arnaldo Carvalho de Melo <[EMAIL PROTECTED]>
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
---
drivers/clocks
Add /debugfs/mctracer/trace to output trace output.
Here's an example of the content.
CPU 0: [] notifier_call_chain+0x16/0x60 <--
[] __atomic_notifier_call_chain+0x26/0x56
CPU 0: [] mce_idle_callback+0x9/0x2f <--
[] notifier_call_chain+0x38/0x60
CPU 0: [] acpi_processor_idle+0x16/0x518
The design is for mcount based tracers to be added thru the
lib/mcount/tracer_interface.h file, just like mcount users should add
themselves to lib/mcount/mcount.h. A Kconfig rule chooses the right MCOUNT and
MCOUNT_TRACER user.
This is to avoid function call costs for something that is supposed t
The following patch series brings to vanilla Linux a bit of the RT kernel
trace facility. This incorporates the "-pg" profiling option of gcc
that will call the "mcount" function for all functions called in
the kernel.
This patch series implements the code for x86 (32 and 64 bit), but
other archs
On Wed, Jan 02, 2008 at 02:12:28PM -0800, Roland McGrath wrote:
> I have no opinions about the config symbol names. Among the existing
> precedents for internal/descriptionless symbols I find more not using the
> HAVE_ prefix than those using it.
The convention is newly established - so no suprise
On Jan 3, 2008 3:24 PM, Jarek Poplawski <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 03, 2008 at 08:06:09AM +0100, Jarek Poplawski wrote:
> > On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
> > > Convert semaphore to mutex in struct class.
> > ...
> > > One lockdep warning detected as follo
On Thu, Jan 03, 2008 at 08:06:09AM +0100, Jarek Poplawski wrote:
> On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
> > Convert semaphore to mutex in struct class.
> ...
> > One lockdep warning detected as following, thus use mutex_lock_nested with
> > SINGLE_DEPTH_NESTING in class_devi
On Wed, Jan 02, 2008 at 08:05:14PM -0800, Harvey Harrison wrote:
Thanks for the cleanup...
...
> diff --git a/arch/x86/mm/fault_32.c b/arch/x86/mm/fault_32.c
> index a2273d4..f2e909b 100644
> --- a/arch/x86/mm/fault_32.c
> +++ b/arch/x86/mm/fault_32.c
> @@ -33,28 +33,6 @@
>
> extern void die(c
On Thu, Jan 03, 2008 at 01:50:20PM +0800, Dave Young wrote:
> Convert semaphore to mutex in struct class.
...
> One lockdep warning detected as following, thus use mutex_lock_nested with
> SINGLE_DEPTH_NESTING in class_device_add
>
> Jan 3 10:45:15 darkstar kernel: ==
From: Ananth N Mavinakayanahalli <[EMAIL PROTECTED]>
Move kprobes examples from Documentation/kprobes.txt to under samples/.
Patch originally by Randy Dunlap.
o Updated the patch to apply on 2.6.24-rc6-mm1
o Modified examples code to build on multiple architectures. Currently,
the examples code
Andi Kleen a écrit :
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
correc
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(con
From: Ananth N Mavinakayanahalli <[EMAIL PROTECTED]>
This patch adds CONFIG_HAVE_KRETPROBES to the 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 pres
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 achieva
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.]
>
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
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 10:47:38.00
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 b/
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 u
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
+++ b/fs/u
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 Lin
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 10:45:
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/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 linux.new
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 linux.new/drivers/ieee1394/nod
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/base/class.c | 22 +++---
drivers/base/core.c| 13 ++---
include/linux/device.h |3 ++-
3 files changed, 19 insertions(+), 19 deletions(-)
diff -upr linux/
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
4-power-stru
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 g
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 potential
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,
Ha
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_O
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 embedde
>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 TOPD
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
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
---
Whe
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 P
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 P
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 t
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:
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
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 c
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, an
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
linux-2.6.24-rc5-rt1-mark/include/linux/netde
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.
> > > > th
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 di
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 r
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.
>
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 an
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
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
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).
>
>
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
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
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 ar
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
--
T
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 +-
arch/
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 inlin
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
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
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
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
> i
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 particula
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: Jam
-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 li
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 ;-)
>
>
[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, 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 i
>-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 ve
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 a
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 ;-)
arch/x86/mm/fault_32.c | 38 +-
arch/x86/m
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 f
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 W
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 whe
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 o
On Jan 3, 2008 12:08 AM, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 1 Jan 2008, Greg KH wrote:
>
> > For most cases, yes, I agree with this, but due to the lockdep issues
> > that occur here, and the whole mess with the suspend path and locking
> > the device tree, that has been hashed out man
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 m
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]
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",
t
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_GP
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 lib
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
--- a/drivers/power
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
+++ linux/arch/x86/mm/f
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 st
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 BIO
.. 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|
1 - 100 of 433 matches
Mail list logo
