I am not sure if this is useful or if this should take a different form
But Eric and Peter asked me for some of the functionality included here.
Cleanup and export the statistics support that is current used to
generate the numbers available via sysfs.
Add a function kmem_cache_count()
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
---
commit 966fef8404d59056d8524bf94d7dff790fe1fa82
tree 1adc274bc9b8e7e420db0b0023c8b70bd294e84e
parent 0cbdc367b144a95709852c642a069ed652989520
author Rolf Eike Beer [EMAIL PROTECTED] Mon, 21 May 2007 22:55:30 +0200
committer Rolf Eike Beer [EMAIL
* Thomas Gleixner [EMAIL PROTECTED] wrote:
Hmm. That's the code in question:
void __init timekeeping_init(void)
{
* Anant Nitya [EMAIL PROTECTED] wrote:
could you also apply the fix for the softirq problem below, to make
sure it does not interact?
Above patch does solve __ soft_irq_pending __ problem. I am running
this patch with kernel 2.6.21.1 since last day doing all kinda things
but haven't
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1, irqs_disabled():0
Call Trace:
[a00100014700] show_stack+0x80/0xa0
sp=e0306e6f7a00 bsp=e0306e6f0ef8
Dan Dennedy wrote:
On Sunday 20 May 2007 08:28, Stefan Richter wrote:
maybe we should change
...
struct raw1394_cycle_timer {
[to consist of two u64 to get same alignment on all architectures]
...
before a libraw1394 with get-cycle-timer support is released.
Shall I prepare according patches
When a non-directory object is accessed without a trailing slash, then
path resolution returns the object itself as usual.
If a non-directory object is accessed with a trailing slash, then the
filesystem may opt to let the file be accessed as a directory. In
this case something (as
Others might suggest accessing streams, resource forks or extended
attributes through such an interface. However this patch only deals
with the non-directory case, so directories would be excluded from
that interface.
here's a possibly stupid question. What about symlinks to dirs?
On Wed, 23 May 2007 16:31:54 +1000 David Chinner [EMAIL PROTECTED] wrote:
Saw this when running strace -f on a script on 2.6.21 on ia64:
BUG: sleeping function called from invalid context at kernel/fork.c:385
in_atomic():1, irqs_disabled():0
Call Trace:
[a00100014700]
On a number of boards the current prereset logic seems to misbehave:
scsi0 : pata_platform
ata1: PATA max PIO0 cmd 0xb06001f0 ctl 0xb06003f6 bmdma 0x irq 0
ata1: device not ready (errno=-19), forcing hardreset
ata1: BUG: prereset() requested invalid reset type
This triggers when there is
This chunk from linux-2.6-utrace.patch breaks PTRACE_SYSEMU, which UML
rather relies on.
PTRACE_SYSEMU and PTRACE_SYSEMU_SINGLESTEP are implemented in a different
way (see kernel/ptrace.c), which does not require that assembly code.
(It also works for free on other arch's if you want to
Here are some USB fixes against your 2.6.22-rc2 tree.
They fix a number of minor and semi-major issues (suspend to ram should
now work properly for everyone that was hitting the USB can't suspend
error) and add a number of new device ids to various USB drivers.
All of these, except for the new
* Chris Wright ([EMAIL PROTECTED]) wrote:
I tracked down a bunch of these a little while back. It's not really
iret_exc, but since there is no _sfixup/_efixup markers iret_exc is the
closest symbol to pick on. All the [iret_exc, _etext] warnings I found
were completely harmless from things
On Wednesday 23 May 2007 12:56 am, Paul Mundt wrote:
On Wed, May 23, 2007 at 12:25:44AM -0400, Rob Landley wrote:
mv arm cris blackfin parisc powerpc s390 x86_64 uml arch
You missed sh, mips, fujitsu/frv, m68k, ia64, i386, and sparc.
Yup. I'll add 'em to the next pass. Thanks.
There's
Make some offending drivers depend on it and set
CONFIG_ARCH_NO_VIRT_TO_BUS for ppc64 so that we don't build those drivers.
Signed-off-by: Stephen Rothwell [EMAIL PROTECTED]
---
arch/powerpc/Kconfig|3 +++
drivers/atm/Kconfig |8
drivers/block/Kconfig |
On Wed, May 23, 2007 at 08:36:04AM +0200, Miklos Szeredi wrote:
Interesting... How do you deal with mount propagation and things like
mount --move?
Moving (or doing other mount operations on) an ancestor shouldn't be a
problem. Moving this mount itself is not allowed, and neither is
On Wed, May 23, 2007 at 05:01:55PM +1000, Stephen Rothwell wrote:
Make some offending drivers depend on it and set
CONFIG_ARCH_NO_VIRT_TO_BUS for ppc64 so that we don't build those drivers.
Seeing how few targets _do_ have that, I'd invert the that. I.e. have
HAS_VIRT_TO_BUS in arch/*/Kconfig
(changing email. My employer server adds a stupid and malformed
disclaimer, so that vger refuses the post. Oh well. I will no trim the
quot to my original message so that it's here for anyone).
On Tue, 2007-05-22 at 15:07 -0700, Linus Torvalds wrote:
On Tue, 22 May 2007, Romano Giannetti
On Tue, May 22 2007, Christoph Lameter wrote:
On Wed, 23 May 2007, Srihari Vijayaraghavan wrote:
(If you want me to test it with other slub or kernel debug options please
let
me know. It just takes a lot of time to eliminate the variables, if there
are
problems.)
Yup. compile
Hi,
I wanted to mail earlier, but I had always something get in my way.
I used cfs v13 since you announced it. Since patching the kernel (2.6.21.1)
with cfs v13
I did the following things;
- big backup of home onto tape and restoring it after changing to reiser4
(yes, I know the threads
(resent, using gmail)
On Mon, 2007-05-21 at 14:25 -0700, Chris Wright wrote:
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
On Mon, 21 May 2007, Chuck Ebbert wrote:
What happened to:
Fix ACPI suspend / device suspend ordering problem
52ade9b3b97fd3bea42842a056fe0786c28d0555
From: Stephen Rothwell [EMAIL PROTECTED]
Date: Wed, 23 May 2007 17:01:55 +1000
Make some offending drivers depend on it and set
CONFIG_ARCH_NO_VIRT_TO_BUS for ppc64 so that we don't build those drivers.
Signed-off-by: Stephen Rothwell [EMAIL PROTECTED]
Acked-by: David S. Miller [EMAIL
From: Al Viro [EMAIL PROTECTED]
Date: Wed, 23 May 2007 08:04:50 +0100
On Wed, May 23, 2007 at 05:01:55PM +1000, Stephen Rothwell wrote:
Make some offending drivers depend on it and set
CONFIG_ARCH_NO_VIRT_TO_BUS for ppc64 so that we don't build those drivers.
Seeing how few targets _do_
Hi,
Yeah, that's racy: once we've sent the signal, the kernel thread can write
NULL to srvTcp-tsk at any time.
Yes, here is another patch :
diff -ur linux/fs/cifs/connect.c linux.new/fs/cifs/connect.c
--- linux/fs/cifs/connect.c 2007-05-23 10:59:13.0 +
+++
On Wed, 23 May 2007 09:09:00 +0200
Romano Giannetti [EMAIL PROTECTED] wrote:
Will try to reboot with clocksource=acpi_pm, althoughI think that this
is the one I'm using.
you can see that with:
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
--
Paolo Ornati
Interesting... How do you deal with mount propagation and things like
mount --move?
Moving (or doing other mount operations on) an ancestor shouldn't be a
problem. Moving this mount itself is not allowed, and neither is
doing bind or pivot_root. Maybe bind could be allowed...
* Hemmann, Volker Armin [EMAIL PROTECTED] wrote:
Hi,
I wanted to mail earlier, but I had always something get in my way.
I used cfs v13 since you announced it. Since patching the kernel
(2.6.21.1) with cfs v13 I did the following things;
[...]
So far I am pretty satisfied. I can't
Hi Al,
On Wed, 23 May 2007 08:04:50 +0100 Al Viro [EMAIL PROTECTED] wrote:
On Wed, May 23, 2007 at 05:01:55PM +1000, Stephen Rothwell wrote:
Make some offending drivers depend on it and set
CONFIG_ARCH_NO_VIRT_TO_BUS for ppc64 so that we don't build those drivers.
Seeing how few targets
On Wed, 23 May 2007, Rob Landley wrote:
On Tuesday 22 May 2007 10:38 pm, Roland Dreier wrote:
I could send a patch to do this, but moving files via patch is icky.
Would it
be better to start a git tree and ask people to pull from it, or to send
in
script snippets like the
Hi,
I am trying to upgrade from my ubuntu kernel 2.6.17.3 to 2.6.21.1 and I
have quite a bunch of problems with suspend/resume, both to disk and to
ram. I have reported the s2ram problem in a separate message (search for
a follow-up to the thread with subject [patch 00/69] -stable review.
* Alexey Kuznetsov [EMAIL PROTECTED] wrote:
Hello!
1. New entries can be added to tsk-pi_state_list after task completed
exit_pi_state_list(). The result is memory leakage and deadlocks.
2. handle_mm_fault() is called under spinlock. The result is obvious.
3. State machine is
Hi,
Paa Paa paapaa125 at hotmail.com writes:
But are you saying that with most desktop mobos one doesn't usually have the
different power states available at all? So basically the only means to
conserve power is to scale the frequency?
Even frequency is very limited on core 2 duo.
On Tue 22-05-07 15:39:31, Eric Sandeen wrote:
Eric Sandeen wrote:
Jan -
I ran 2.6.21 + your udf patches from -mm through some udf tests which,
oddly enough, can be found in the xfstests test suite in xfsprogs cvs
from sgi.
It looks much better than before, but I was able to trip
On Wed, May 23, 2007 at 09:19:17AM +0200, Miklos Szeredi wrote:
Eh... Arbitrary limitations are fun, aren't they?
But these mounts _are_ special. There is really no point in moving or
pivoting them.
pivoting - probably true, moving... why not?
What about MNT_SLAVE stuff being set up
On Wed, 2007-05-23 at 09:19 +0200, Paolo Ornati wrote:
On Wed, 23 May 2007 09:09:00 +0200
Romano Giannetti [EMAIL PROTECTED] wrote:
Will try to reboot with clocksource=acpi_pm, althoughI think that this
is the one I'm using.
you can see that with:
cat
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
- A new readahead patch series. This needs serious review and performance
testing please.
- Added Ingo's CFS CPU scheduler
- Xen dom-U support is now in the x86 tree.
Boilerplate:
- See the
On Wed, 23 May 2007 00:42:33 -0700 Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
This is intermittently getting resume-from-RAM failures. It is not
sufficiently repeatable to be able to bisect.
[ 1381.119362]
Andrew Morton wrote:
But we'd expected and hoped that flash-based XIP would be able to use
the existing xip infrastructure, in mm/filemap_xip.c. Not possible?
Thanks for the heads up Andrew. Reading the cramfs patch, I've found a
lot of similarities between the current mainline xip stack and
On Wed, 23 May 2007 08:50:01 +1000
Con Kolivas [EMAIL PROTECTED] wrote:
On Wednesday 23 May 2007 06:42, Ash Milsted wrote:
Hi. I just did some video encoding on my desktop and I was noticing
(for the first time in a while) that running apps had to hit swap quite
a lot when I switched to
On Wed, 2007-05-23 at 07:23 +0200, Michael Gerdau wrote:
For me the huge difference you have for sd to the others increases the
likelyhood the glxgears benchmark does not measure scheduling of graphic
but something else.
I think some people forget that X11 has its own scheduler for graphics
On Tue, 2007-05-22 at 17:25 -0700, Williams, Dan J wrote:
The approach I have taken is to add the missing definitions to
include/asm-s390/dma-mapping.h [ a non-outlook-mangled version of the
patch is pushed out in my rebased git tree ]. I was not able to fully
compile-test this change as the
Eh... Arbitrary limitations are fun, aren't they?
But these mounts _are_ special. There is really no point in moving or
pivoting them.
pivoting - probably true, moving... why not?
I don't see any use for that. But indeed, it should not be too hard
to do.
What about MNT_SLAVE
Paul Mundt wrote:
On a number of boards the current prereset logic seems to misbehave:
scsi0 : pata_platform
ata1: PATA max PIO0 cmd 0xb06001f0 ctl 0xb06003f6 bmdma 0x irq 0
ata1: device not ready (errno=-19), forcing hardreset
ata1: BUG: prereset() requested invalid reset type
Greg KH wrote:
On Mon, May 21, 2007 at 10:31:01AM +0530, Maneesh Soni wrote:
On Thu, May 17, 2007 at 08:16:10PM +0200, Tejun Heo wrote:
Allowing attribute and symlink dentries to be reclaimed means
sd-s_dentry can change dynamically. However, updates to the field
are unsynchronized leading
On Wed, May 23, 2007 at 09:58:35AM +0200, Xavier Bestel wrote:
On Wed, 2007-05-23 at 07:23 +0200, Michael Gerdau wrote:
For me the huge difference you have for sd to the others increases the
likelyhood the glxgears benchmark does not measure scheduling of graphic
but something else.
I
Hi,
This contains LZO1X-1 compressor and LZO1X decompressor (safe and
standard version).
This includes changes suggested by various people - Thanks to all who
reviewed previous patches for this LZO port.
Changelog vs original LZO 2.02 code:
- Chopped down huge parts of original code that were
On Wed, May 23, 2007 at 10:05:21AM +0200, Miklos Szeredi wrote:
Er... These mounts might not be propagated, but what about a bind
over another instance of such file in master tree?
So your question is, which mount takes priority on the lookup? It
probably should be the propagated real
Hi Jeff:
Could you please review this patch? Sorry for miss sending the patch to
you for review at beginning.
Thanks a lot
-Bryan Wu
On Sun, 2007-05-06 at 14:50 -0700, [EMAIL PROTECTED] wrote:
From: Wu, Bryan [EMAIL PROTECTED]
This patch implements the driver necessary use the Analog
On Wed, May 23, 2007 at 10:07:08AM +0200, Tejun Heo wrote:
Paul Mundt wrote:
On a number of boards the current prereset logic seems to misbehave:
scsi0 : pata_platform
ata1: PATA max PIO0 cmd 0xb06001f0 ctl 0xb06003f6 bmdma 0x irq 0
ata1: device not ready (errno=-19), forcing
Hi,
Sorry for the wrong patch in my last post.
How about save the tsk then call kthread_stop like this:
diff -udr linux/fs/cifs/connect.c linux.new/fs/cifs/connect.c
--- linux/fs/cifs/connect.c 2007-05-23 10:59:13.0 +
+++ linux.new/fs/cifs/connect.c 2007-05-23 16:33:54.0
On 5/23/07, Krzysztof Halasa [EMAIL PROTECTED] wrote:
Robert P. J. Day [EMAIL PROTECTED] writes:
that may be but, as i suggested earlier, that would get into guessing
what those developers were thinking, and i just didn't want to go
there.
No guessing, I just checked it (though a second
On Wed, 23 May 2007 10:05:39 +0200,
Martin Schwidefsky [EMAIL PROTECTED] wrote:
We are trying to get rid of dma-mapping.h, see the last change to the
file with commit 411f0f3edc141a582190d3605cadd1d993abb6df. I don't think
we should reintroduce dma related definition but split the async_tx in
On Tue, 22 May 2007, Andrew Morton wrote:
This patch is using mmap()'s randomization functionality in such a way
that it maps the main executable of (specially compiled/linked
-pie/-fpie) ET_DYN binaries onto a random address (in cases in which
mmap() is allowed to perform a
This does not happen in reality. Breakpoints can only be set by the
debugger, not by the program itself. The debugger should always eat the
trap.
Hmmm. I put in a little extra code to account for the possibility that
a program might want to set hardware breakpoints in itself. Should
On Wednesday, 23 May 2007 03:48, Matt Mackall wrote:
On Tue, May 22, 2007 at 09:19:43PM -0300, Henrique de Moraes Holschuh wrote:
On Tue, 22 May 2007, Matt Mackall wrote:
On Mon, May 21, 2007 at 08:03:49PM -0300, Henrique de Moraes Holschuh
wrote:
On Mon, 21 May 2007, Matt Mackall
On Wed, 2007-05-23 at 10:46 +0200, Cornelia Huck wrote:
Taking a quick look at the async_*.c stuff, the functions in question
basically seem to be of the form
check_if_we_can_do_it_async();
if (async_ok) {
/* do async stuff */
/* that's where the dma mapping creeps in */
}
On Tuesday 22 May 2007 23:09:39 Richard Griffiths wrote:
Venerable cramfs fs Linear XIP patch originally from MontaVista, used in
the embedded Linux community for years, updated for 2.6.21. Tested on
several systems with NOR Flash. PXA270, TI OMAP2430, ARM Versatile and
Freescale iMX31ADS.
Hi,
On Wednesday, 23 May 2007 09:25, Romano Giannetti wrote:
Hi,
I am trying to upgrade from my ubuntu kernel 2.6.17.3 to 2.6.21.1 and I
have quite a bunch of problems with suspend/resume, both to disk and to
ram. I have reported the s2ram problem in a separate message (search for
a
On Wed, May 23, 2007 at 10:05:21AM +0200, Miklos Szeredi wrote:
Er... These mounts might not be propagated, but what about a bind
over another instance of such file in master tree?
So your question is, which mount takes priority on the lookup? It
probably should be the propagated
Bryan Wu wrote:
Hi Jeff:
Could you please review this patch? Sorry for miss sending the patch to
you for review at beginning.
can you resend as a patch rather than a quoted patch?
Jeff
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Wed, 2007-05-23 at 05:13 -0400, Jeff Garzik wrote:
Bryan Wu wrote:
Hi Jeff:
Could you please review this patch? Sorry for miss sending the patch to
you for review at beginning.
can you resend as a patch rather than a quoted patch?
Jeff
Oh, sorry, I forgot this. It
On 5/23/07, Miklos Szeredi [EMAIL PROTECTED] wrote:
So your question is, which mount takes priority on the lookup? It
probably should be the propagated real mount, rather than the
dir-on-file one, shouldn't it?
Maybe this might belong into __link_path_walk() similar to the
handling of
On Wednesday, 23 May 2007 09:48, Andrew Morton wrote:
On Wed, 23 May 2007 00:42:33 -0700 Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
This is intermittently getting resume-from-RAM failures. It is not
On 5/23/07, Miklos Szeredi [EMAIL PROTECTED] wrote:
As for unlink... How do you deal with having that thing
mounted, mounting something _under_ it (so that vfsmount would be kept
busy) and then unlinking that sucker?
Yeah, that's a good point. Current patch doesn't deal with that.
On Tue, May 22, 2007 at 04:41:36PM -0700, Kevin Hilman wrote:
On Tue, 2007-05-22 at 16:25 -0700, Daniel Walker wrote:
On Tue, 2007-05-22 at 16:01 -0700, Kevin Hilman wrote:
Add a preempt_enable() to flush_tlb_kernel_page() since -rt4 patch
adds a preempt_disable but no preempt_enable().
On Tue, May 22, 2007 at 04:31:22PM -0700, Jesse Barnes wrote:
On Tuesday, May 22, 2007, Wayne Sherman wrote:
If so, the D-Link is not being mapped into the
right region, and the bridge it is behind does not have enough memory
assigned to it (ff50-ff5f : PCI Bus #02).
Sounds
From: Wu, Bryan [EMAIL PROTECTED]
This patch implements the driver necessary use the Analog Devices
Blackfin processor's on-chip ethernet MAC controller.
Signed-off-by: Bryan Wu [EMAIL PROTECTED]
Cc: Jeff Garzik [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
Paul Mundt wrote:
On Wed, May 23, 2007 at 10:07:08AM +0200, Tejun Heo wrote:
Paul Mundt wrote:
On a number of boards the current prereset logic seems to misbehave:
scsi0 : pata_platform
ata1: PATA max PIO0 cmd 0xb06001f0 ctl 0xb06003f6 bmdma 0x irq 0
ata1: device not ready
So your question is, which mount takes priority on the lookup? It
probably should be the propagated real mount, rather than the
dir-on-file one, shouldn't it?
Maybe this might belong into __link_path_walk() similar to the
handling of symbolic links. If the real mount has always higher
As for unlink... How do you deal with having that thing
mounted, mounting something _under_ it (so that vfsmount would be kept
busy) and then unlinking that sucker?
Yeah, that's a good point. Current patch doesn't deal with that.
Simplest solution could be to disallow submounting
(Adding Dmitry to CC so that he doesn't miss it.
Also, if you'd like to get your patch merged, you should add proper
Signed-off-by line.
Thanks)
On Wed, 23 May 2007, Renato Golin wrote:
This small patch adds the automatic recalibration feature without
spoiling previously calibrated devices.
Hi,
Andrew Morton napisał(a):
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc2/2.6.22-rc2-mm1/
Christoph, this looks like a bug in SLUB.
[ 16.232377] PM: Adding info for No Bus:vcs1
[ 16.237588] PM: Adding info for No Bus:vcsa1
[ 18.683210] PM: Adding info for
On Wed, May 23, 2007 at 11:29:37AM +0200, Tejun Heo wrote:
Paul Mundt wrote:
On Wed, May 23, 2007 at 10:07:08AM +0200, Tejun Heo wrote:
Paul Mundt wrote:
On a number of boards the current prereset logic seems to misbehave:
scsi0 : pata_platform
ata1: PATA max PIO0 cmd 0xb06001f0 ctl
On Tue, May 22, 2007 at 08:48:49PM +0200, Miklos Szeredi wrote:
*/
-static int __follow_mount(struct path *path)
+static int __follow_mount(struct path *path, bool enter)
{
int res = 0;
while (d_mountpoint(path-dentry)) {
- struct vfsmount *mounted =
On Wed, 2007-05-23 at 11:05 +0200, Rafael J. Wysocki wrote:
Hi,
On Wednesday, 23 May 2007 09:25, Romano Giannetti wrote:
http://lkml.org/lkml/2007/5/23/38
Please see http://bugzilla.kernel.org/show_bug.cgi?id=8456
That seems to resemble the symptoms you describe.
No, I don't think.
On Wed, May 23, 2007 at 11:03:08AM +0200, Miklos Szeredi wrote:
I still don't get it where the superblock comes in. The locking is
interesting in there, yes. And I haven't completely convinced
myself it's right, let alone something that won't easily be screwed up
in the future. So there's
During prereset, -ENODEV return from ata_wait_ready() is not an error.
This causes unnecessary bug message on controllers which uses 0xff to
indicate empty port. Fix it.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
Cc: Paul Mundt [EMAIL PROTECTED]
---
This one is for 2.6.22 too. Thanks.
On 23/05/07, Jiri Kosina [EMAIL PROTECTED] wrote:
(Adding Dmitry to CC so that he doesn't miss it.
Also, if you'd like to get your patch merged, you should add proper
Signed-off-by line.
Hi Jiri,
Sorry, it's my first kernel patch, how do I add Signed-off-by line?
I did with:
$ diff -u
Track lock hold times - that is the time we held the lock.
/proc/lock_holdtime - starts with the same three colums as lock_contentions:
class name (write) contentions read contentions
After that come two times four more columns:
nr min max total
for both (write) locks and read locks.
Allow for runtime configuration of lockdep and lockstat.
/proc/sys/kernel/prove_locking
/proc/sys/kernel/lock_stat
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
kernel/lockdep.c | 27 +++
kernel/sysctl.c | 27 +++
2 files changed,
Rework the lock stat counters to be scalable.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/lockdep.h | 34 +-
kernel/lockdep.c| 162
kernel/lockdep_proc.c | 136 ++--
3
Put the lock dependancy tracking bits under CONFIG_PROVE_LOCKING
This way we can reuse the hold_lock part of lockdep for other purposes.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
kernel/lockdep.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
Index:
Track lock waittime - that is the time spend waiting on lock acquisition.
/proc/lock_waittime - starts with the same three colums as lock_contentions:
class name (write) contentions read contentions
After that come two times four more columns:
nr min max total
for both (write) contentions
Use the lockdep infrastructure to track lock contention and other lock
statistics.
It tracks lock contention events, and the first four unique call-sites that
encountered contention.
It also measures lock wait-time and hold-time in nanoseconds. The minimum and
maximum times are tracked, as well
Count lock contention events per lock class. Additionally track the first four
callsites that resulted in the contention.
/proc/lock_contentions - gives a single line per lock class:
class name (write) contentions read contentions
Followed by another three columns per contention point:
raw_spinlock_t should not use lockdep (and doesn't) since lockdep itself relies
on it.
Signed-off-by: Peter Zijlstra [EMAIL PROTECTED]
---
include/linux/spinlock_types.h|4 ++--
include/linux/spinlock_types_up.h |9 +
2 files changed, 3 insertions(+), 10 deletions(-)
Index:
This small patch adds the automatic recalibration feature without
spoiling previously calibrated devices. It's a fix for those joysticks
that report faulty range, specially Saitek Cyborg Evo Force.
File: drivers/input/joydev.c
Fix:
- extracted code from joydev_connect to method
+ * This is called if the object has no -lookup() defined, yet the
+ * path contains a slash after the object name.
+ *
+ * If the filesystem defines an -enter() method, this will be called,
+ * and the filesystem shall fill the supplied struct path or return an
+ * error.
+ *
+ *
On Wed, May 23, 2007 at 11:03:08AM +0200, Miklos Szeredi wrote:
I still don't get it where the superblock comes in. The locking is
interesting in there, yes. And I haven't completely convinced
myself it's right, let alone something that won't easily be screwed up
in the future. So
--- Christoph Lameter [EMAIL PROTECTED] wrote:
On Wed, 23 May 2007, Srihari Vijayaraghavan wrote:
[...]
Yup. compile with
CONFIG_NUMA
CONFIG_LOCKDEP
CONFIG_DEBUG_LOCK_ALLOCS
(All the tests in this email was conducted on top of your patch)
Yup done that. The resulting kernel (without
Hello,
As per the recent discussion, the folowing patch removes the TIF_NOTIFY_RESUME
flag from all processor architectures. The flag was not used except on IA-64
for the perfmon subsystem. For IA-64, the patch replaces the flag with a new
dedicated TIF flag. This provides an extra low-order bit
On Wed, May 23, 2007 at 12:09:19PM +0200, Miklos Szeredi wrote:
Right. After locking vfsmount_lock, mount_dironfile() should recheck
if there was a race and bail out.
Owww... Not pretty, that...
I don't think the filesystem ought to try _creating_ a vfsmount. I
imagine, that the fs has
+ * This is tricky, because for namespace modification we must take the
+ * namespace semaphore. But mntput() is called from various places,
+ * sometimes with namespace_sem held. Fortunately in those places the
+ * mount cannot yet have MNT_DIRONFILE, or at least that's what I
+
* Peter Zijlstra [EMAIL PROTECTED] wrote:
Use the lockdep infrastructure to track lock contention and other lock
statistics.
It tracks lock contention events, and the first four unique call-sites
that encountered contention.
It also measures lock wait-time and hold-time in
On Tue, May 22, 2007 at 08:35:17AM -0400, Shaya Potter wrote:
Bharata B Rao wrote:
In case of regular files, when we copyup a file, we are actually preventing
any writes to the lower layers (which we have designated as read only).
Applying the same logic to devices, what do we achieve by
On 23 May 2007, at 09:27, Nitin Gupta wrote:
This contains LZO1X-1 compressor and LZO1X decompressor (safe and
standard version).
I understand that the 'safe' decompression code is 'somewhat slower'
and that decompressor performance is a key feature of this algorithm.
However, I am
Ingo Molnar wrote:
if you feel inclined to try the git-bisection then by all means please
do it (it will certainly be helpful and educative), but it's optional: i
dont think you should 'need' to go through extra debugging chores, my
analysis based on the excellent trace you provided still
-Message d'origine-
De : Greg KH [mailto:[EMAIL PROTECTED]
Envoyé : 22 mai 2007 23:37
À : Fortier,Vincent [Montreal]
On Tue, May 22, 2007 at 09:28:34PM -0400, Fortier,Vincent
[Montreal] wrote:
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Randy Dunlap wrote:
Add notime boot option to prevent timing data from being printed on
each printk message line.
That's a good source of confusion. To me, notime means something
like don't bother calculating time, instead of the proposed
behavior. Can't it be something like 'nologts' (no
* Patrick McHardy [EMAIL PROTECTED] wrote:
How is this trace to be understood? Is it simply a call trace in
execution-order? [...]
yeah. There's a help section at the top of the trace which explains the
other fields too:
_--= CPU#
/ _-= irqs-off
1 - 100 of 1026 matches
Mail list logo
