Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
..
I *still* get very slow resume-from-RAM quite often here
(new in 2.6.23 kernel, wasn't there in early 2.6.23-rc*).
..
Something eventually times out after a minute or so
and it comes back. Cannot make it happen reliably,
unless
FILE SYSTEMS===
ext4: delalloc space accounting problem drops data
http://bugzilla.kernel.org/show_bug.cgi?id=9329
Kernel: 2.6.24-rc1
No response from developers
Actually, there has been a response (Eric asked in mailing list and
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
bisect build bugs via a simple shell command around git-bisect
On Tue, 13 Nov 2007 17:55:25 +0100
Ernst Herzberg [EMAIL PROTECTED] wrote:
This pcmcia-card (UMTS Modem) only works if it shares his interrupt with
another device, eg an usb mice. Moving the mice increases the connection
speed, unplugging hangs the connection.
Thats consistent with the card
Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
boot (ARM, Timer)
Hi Eric,
Eric Dumazet wrote:
Instead of using less RAM, you could just boot with rhash_entries=1024
to lower the size of this table.
I just tried that and it seems to reduce the scan time. This is the
result for the first 40 minutes of runtime:
[EMAIL PROTECTED]:/# /tmp/wait.rt
looping 1
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm kernels (I
know
Hello,
On Tue, Nov 13, 2007 at 10:35:11AM -0500, William Cohen wrote:
Robert Richter wrote:
On 10.11.07 21:32:39, Andi Kleen wrote:
It would be really good to extract a core perfmon and start with
that and then add stuff as it makes sense.
e.g. core perfmon could be something simple
Hi Clemens,
Clemens Koller wrote:
This is precisely the sort of thing that BIOS/firmware-level SMI
handlers do, particularly those that have monitoring or management
features. Try to determine if the kernel is doing anything during this
time. If the entire kernel seems to be frozen,
Robert Richter wrote:
On 13.11.07 13:02:08, Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:44:43PM +0100, Robert Richter wrote:
x86 CPU specific code is currently implemented in different ways for
64 and 32 bit. While there are almost no CPU specific files for 64
bit, there is the
Hello,
when I run oprofile like:
opcontrol --reset
opcontrol --start
I just see (hand-copied from screen):
Using default event: CPU_CLK_UNHALTED:10:0:1:1
Using 2.6+ OProfile kernel interface.
Reading module info.
Using log file ...
Daemon started.
And then it hangs the machine hard -
On Tue, Nov 13, 2007 at 03:15:53AM -0800, Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich [EMAIL PROTECTED]
wrote:
PLATFORM===
xipImage is built so that uBoot cant run it (ARM)
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection of
a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
On Tue, Nov 13, 2007 at 05:07:21PM +0100, Thomas Gleixner wrote:
On Tue, 13 Nov 2007, Mark Lord wrote:
Andrew Morton wrote:
On Mon, 12 Nov 2007 22:42:32 -0800 Natalie Protasevich
[EMAIL PROTECTED] wrote:
..
with CONFIG_NO_HZ and/or CONFIG_HPET_TIMER set kernel 2.6.23 doesn't
On Tue, 2007-11-13 at 12:50 -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we can autonomouly
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection of
a bug was a very laborous task so that it was only used as a final,
last-ditch approach for really nasty bugs. Today we
One more thing. Here is my daemonrc:
SESSION_DIR=/var/lib/oprofile
NR_CHOSEN=0
SEPARATE_LIB=0
SEPARATE_KERNEL=0
SEPARATE_THREAD=0
SEPARATE_CPU=0
VMLINUX=/home/jack/source/linux-2.6-linus/vmlinux
IMAGE_FILTER=
CPU_BUF_SIZE=0
CALLGRAPH=8
KERNEL_RANGE=c01000a0,c029f508
XENIMAGE=none
And when
Thomas - what is way forward here?
I consider the patch serie ready to be applied and I
leave it to you (x86 guys) to decide the way forward to mainline.
cleanup - mm - linus or straight to linus.
If there is any concerns (from you or others) please let
me know so we can get it fixed.
And I
Given the wide range of ARM platforms today, it is utterly idiotic to
expect a single person to be able to provide responses for all ARM bugs.
I for one wish I'd never *VOLUNTEERED* to be a part of the kernel
bugzilla, and really *WISH* I could pull out of that function.
You can. Perhaps that
PORTA and PORTB have odr registers, as well. However, the PORTB odr
register is only 16bit.
Signed-off-by: Jochen Friedrich [EMAIL PROTECTED]
---
arch/powerpc/sysdev/commproc.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/sysdev/commproc.c
Jan Kara wrote:
Hello,
A one-time event thus far, happened under very heavy I/O,
Dell i9400 Core2Duo notebook w/3GB ram, single SATA drive with ext3.
Had to cycle power to get it back and see this Oops in the syslog:
..
Hmm, your pointer to buffer_head in journal_head has been
On Tue, 2007-11-13 at 16:34 +0800, Zhang, Yanmin wrote:
My new bisect captured 7c9e69faa28027913ee059c285a5ea8382e24b5d
which caused the regression of iozone following run (3rd/4th... run after
mounting
the ext3 partition).
Linus just reverted that commit with commit:
commit
If fs_enet is build as module, on PPC_CPM_NEW_BINDING platforms
mii-fec/mii-bitbang should be build as module, as well. On other
platforms, mii-fec/mii-bitbang must be included into the main module.
Otherwise some symbols remain undefined. Additionally, fs_enet uses
libphy, so add a select
Hello,
On Tue, Nov 13, 2007 at 04:17:18PM +0100, Robert Richter wrote:
On 10.11.07 21:32:39, Andi Kleen wrote:
It would be really good to extract a core perfmon and start with
that and then add stuff as it makes sense.
e.g. core perfmon could be something simple like just support
to
On Tue, Nov 13, 2007 at 09:01:29AM -0800, Greg KH wrote:
I'm still not sold on this idea at all. I'm really betting that there
is a lot of incorrect acpi slot information floating around in machines
and odd things will show up in these slot entries.
Is that the end of the world? Instead of
On Tue, Nov 13, 2007 at 01:18:43PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
Ingo Molnar wrote:
for example git-bisect was godsent. I remember that years ago bisection
of a bug was a very laborous task so that it was only used as a
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
It's a 540MByte download over a slow link for everyone else.
Where do you get this number from?
$ du -sh .git/objects/pack/
249M.git/objects/pack/
$ du -sh .git/objects/
253M.git/objects/
ie about half what you claim.
--
Intel
Stephane Eranian wrote:
Hello,
On Tue, Nov 13, 2007 at 10:35:11AM -0500, William Cohen wrote:
Robert Richter wrote:
On 10.11.07 21:32:39, Andi Kleen wrote:
It would be really good to extract a core perfmon and start with
that and then add stuff as it makes sense.
e.g. core perfmon could be
Describes the format string standard further: Use of field names before the type
specifiers..
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
Documentation/markers.txt |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Index: linux-2.6-lttng/Documentation/markers.txt
Upon module load, we must take the markers mutex. It implies that the marker
mutex must be nested inside the module mutex.
It implies changing the nesting order : now the marker mutex nests inside the
module mutex. Make the necessary changes to reverse the order in which the
mutexes are taken.
Hi Andrew,
Here are some fixes for the Linux Kernel Markers present in 2.6.24-rc2-git3.
There is a code path (module load) that may update markers without holding the
markers mutex, si I fixed that. The rest is just an tiny documentation
improvement.
The patchset applies on top of
On Tue, Nov 13, 2007 at 09:36:42AM -0200, Glauber de Oliveira Costa wrote:
-BEGIN PGP SIGNED MESSAGE-
And the EM64T based comment is wrong because there are AMD based
vSMPs too.
Just got it as-is from the old Kconfig. Do you think it should be fixed
as well?
Yep.
Thanks,
Kiran
-
To
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
It's a 540MByte download over a slow link for everyone else.
Where do you get this number from?
$ du -sh .git/objects/pack/
249M.git/objects/pack/
$ du -sh .git/objects/
253M.git/objects/
ie about half
QLogic InfiniPath: convert the semaphore ipath_eep_sem to the mutex
API
Signed-off-by: Matthias Kaehlcke [EMAIL PROTECTED]
--
diff --git a/drivers/infiniband/hw/ipath/ipath_eeprom.c
b/drivers/infiniband/hw/ipath/ipath_eeprom.c
index e7c25db..a5b6299 100644
---
Add the field names to marker example format string.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
samples/markers/marker-example.c |3 ++-
samples/markers/probe-example.c |2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
Index:
i get these errors in the kernel log while trying to copy a file from an
iso9660 file system (/dev/sr0) to my intenal hard disk. This is the
second cd/dvd that gives me this error. kernel 2.6.23 works without any
problems, so i think this is not an medium error:
ISO 9660 Extensions: Microsoft
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
Definitely useful, no question.
But the problem is now that kernel devs are addicted to
Hi Andrew,
Here is a repost of the Text Edit Lock. It is required by the immediate values.
It applies on top of 2.6.24-rc2-git3 in this order :
#Text Edit Lock
#for -mm
kprobes-use-mutex-for-insn-pages.patch
kprobes-dont-use-kprobes-mutex-in-arch-code.patch
Add initialization of an array, which needs brackets that would pollute kernel
code, to kernel.h. It is used to declare arguments passed as function parameters
such as:
text_poke(addr, INIT_ARRAY(unsigned char, 0xf0, len), len);
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
Standardize DEBUG_RODATA, removing special cases for hotplug and kprobes.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: Andi Kleen [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
arch/x86_64/mm/init.c | 23 +--
1 file changed, 5 insertions(+), 18 deletions(-)
Index:
On Tue, 13 Nov 2007 09:46:08 -0800 Martin Bligh [EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9267
Kernel: 2.6.23.1
No response from developers
Urm, well, if no-one ever tells the SCSI list it's unrealistic to expect
anyone to be working on it. As far as
Standardize DEBUG_RODATA, removing special cases for hotplug and kprobes.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: Andi Kleen [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
arch/x86/mm/init_32.c | 20 +++-
1 file changed, 7 insertions(+), 13 deletions(-)
Index:
This is an architecture independant synchronization around kernel text
modifications through use of a global mutex.
A mutex has been chosen so that kprobes, the main user of this, can sleep during
memory allocation between the memory read of the instructions it must replace
and the memory write
Remove the kprobes mutex from kprobes.h, since it does not belong there. Also
remove all use of this mutex in the architecture specific code, replacing it by
a proper mutex lock/unlock in the architecture agnostic code.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Acked-by: Ananth N
Use the mutual exclusion provided by the text edit lock in the kprobes code. It
allows coherent manipulation of the kernel code by other subsystems.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Acked-by: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL
Fix a memcpy that should be a text_poke (in apply_alternatives).
Use kernel_wp_save/kernel_wp_restore in text_poke to support DEBUG_RODATA
correctly and so the CPU HOTPLUG special case can be removed.
clflush all the cachelines touched by text_poke.
Add text_poke_early, for alternatives and
Make kprobes use INIT_ARRAY().
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Tested-by: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
CC: Andi Kleen [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
arch/x86/kernel/kprobes_32.c |
Make kprobes use INIT_ARRAY().
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Tested-by: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
CC: Andi Kleen [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
arch/x86/kernel/kprobes_64.c |
Protect the instruction pages list by a specific insn pages mutex, called in
get_insn_slot() and free_insn_slot(). It makes sure that architectures that does
not need to call arch_remove_kprobe() does not take an unneeded kprobes mutex.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Since it will not be used by other kernel objects, it makes sense to declare it
static.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Acked-by: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
Matthew Wilcox wrote:
ie about half what you claim.
..
No, it's from earlier in this very thread:
Adrian Bunk wrote:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
..
mkdir t
cd t
git
On Tue, Nov 13, 2007 at 02:09:41PM +0100, Andi Kleen wrote:
If vsmp is selected, PARAVIRT will be too, and the interrupt code will
be patched.
the vsmp option triggers a select statement.
the ifdef only exists because, as I said, the code itself will be always
compiled in, to avoid an
On Tue, Nov 13, 2007 at 11:33:53AM -0700, Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 09:01:29AM -0800, Greg KH wrote:
I'm still not sold on this idea at all. I'm really betting that there
is a lot of incorrect acpi slot information floating around in machines
and odd things will show up
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
mkdir t
cd t
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(wait half an hour)
/usr/bin/du -s linux-2.6
522732 linux-2.6
You're assuming that everything in linux-2.6 was
On Tue, Nov 13, 2007 at 11:33:44AM -0600, Larry Finger wrote:
I'm very encouraged to read of your expanded testing efforts. As a
bcm43xx developer, Ubuntu has been our problem distro, mostly
because your standard kernels have debugging turned off for bcm43xx.
When a Ubuntu user reports a
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote:
On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote:
Btw, I used to test every -mm kernel. But since I've switched distros
(gentoo-ubuntu)
and I have less time, I feel it's harder to test -rc or -mm
On Tue, Nov 13, 2007 at 10:47:45AM -0800, Philip Mucci wrote:
Hi folks,
Well, I can say the mood here at supercomputing'07 is pretty somber in
regards to the latest exchange of messages regarding the perfmon patches.
somber?
Why?
We (a number of the kernel developers) want to see the
Hi Andrew,
Here is the latest version of the Immediate Values. It supports x86 as a single
architecture. I also removed the *_early API which could have been confusing to
developers : choosing the right algorithm is now done internally by keeping
track of where we are in the kernel boot process.
Use immediate values with lower d-cache hit in optimized version as a
condition for scheduler profiling call.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
drivers/kvm/kvm_main.c |3 ++-
include/linux/profile.h |5 +++--
kernel/profile.c| 22 +++---
Changelog:
- Remove immediate_set_early (removed from API).
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
Documentation/immediate.txt | 221
1 file changed, 221 insertions(+)
Index: linux-2.6-lttng/Documentation/immediate.txt
Immediate values are used as read mostly variables that are rarely updated. They
use code patching to modify the values inscribed in the instruction stream. It
provides a way to save precious cache lines that would otherwise have to be used
by these variables.
There is a generic _immediate_read()
PowerPC optimization of the immediate values which uses a li instruction,
patched with an immediate value.
Changelog:
- Put immediate_set and _immediate_set in the architecture independent header.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: Christoph Hellwig [EMAIL PROTECTED]
---
Immediate values provide a way to use dynamic code patching to update variables
sitting within the instruction stream. It saves caches lines normally used by
static read mostly variables. Enable it by default, but let users disable it
through the EMBEDDED menu with the Disable immediate values
In assembly code and in gcc inline assembly, we need .long to express a c long
type on i386 and a .quad to express the same on x86_64. Use macros similar to
powerpc PPC_LONG to express those. Name chosen: ASM_LONG. (didn't feel like
X86_LONG was required)
This is useful in inline assembly within
Since the breakpoint handler is useful both to kprobes and immediate values, it
makes sense to make the required restore_interrupt() available through
asm-i386/kdebug.h.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Acked-by: Ananth N Mavinakayanahalli [EMAIL PROTECTED]
CC: Christoph Hellwig
x86 optimization of the immediate values which uses a movl with code patching
to set/unset the value used to populate the register used as variable source.
Changelog:
- Use text_poke_early with cr0 WP save/restore to patch the bypass. We are doing
non atomic writes to a code region only touched
On Tue, 13 Nov 2007 04:32:07 -0800 (PST) David Miller [EMAIL PROTECTED] wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 04:12:59 -0800
On Tue, 13 Nov 2007 03:58:24 -0800 (PST) David Miller [EMAIL PROTECTED]
wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
Definitely useful, no
On Monday 12 November 2007, eric miao wrote:
Hi David,
I hope I was not late giving my humble feedback on this framework :-)
Can we use per gpio based structure instead of per gpio_chip based one,
just like what the generic IRQ layer is doing nowadays?
We can do most anything. What would
Mathieu Desnoyers wrote:
In assembly code and in gcc inline assembly, we need .long to express a c long
type on i386 and a .quad to express the same on x86_64. Use macros similar to
powerpc PPC_LONG to express those. Name chosen: ASM_LONG. (didn't feel like
X86_LONG was required)
In the x86
Hi Andrew,
Those are the new features I plan to add to the Markers :
- Support multiple probes per marker (so blktrace, LTTng, SystemTAP and others
can coexist peacefully)
- Export the markers to a Module.markers file in modpost (for Systemtap)
- Use the Immediate values to optimize the branch
RCU style multiple probes support for the Linux Kernel Markers.
Common case (one probe) is still fast and does not require dynamic allocation
or a supplementary pointer dereference on the fast path.
- Move preempt disable from the marker site to the callback.
Since we now have an internal
Make markers use immediate values.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
Documentation/markers.txt | 17 +
include/linux/marker.h| 42 --
kernel/marker.c |8 ++--
kernel/module.c |1 +
This adds some new magic in the MODPOST phase for CONFIG_MARKERS.
Analogous to the Module.symvers file, the build will now write a
Module.markers file when CONFIG_MARKERS=y is set. This file lists
the name, defining module, and format string of each marker,
separated by \t characters. This
Andrew Morton wrote:
On Fri, 21 Sep 2007 10:55:05 +0530 Aneesh Kumar K.V [EMAIL PROTECTED] wrote:
Also add generic_find_next_le_bit
This gets used by the ext4 multi block allocator patches.
arm allmodconfig:
fs/ext4/mballoc.c: In function `ext4_mb_generate_buddy':
fs/ext4/mballoc.c:836:
Mathieu Desnoyers wrote:
- Use =g constraint for char immediate value inline assembly.
=g is the same as =rmi which is inherently bogus. In your actual
code you use =r, the correct constraint is =q.
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
undebuggable problems debuggable and fixable.
..
[...]
kallsyms returns the first symbol encountered, even though it is weak,
when it should in fact return sys_ni_syscall.
Is it a concern for anyone else out there ? Would it make sense to fix
it ?
I don't know if it is a concern, but if we're going to fix it, we should
probably do it in
* Mathieu Desnoyers ([EMAIL PROTECTED]) wrote:
[...]
kallsyms returns the first symbol encountered, even though it is weak,
when it should in fact return sys_ni_syscall.
Is it a concern for anyone else out there ? Would it make sense to fix
it ?
I don't know if it is a concern, but if
Hi folks,
Well, I can say the mood here at supercomputing'07 is pretty somber
in regards to the latest exchange of messages regarding the perfmon
patches. Our community has been the largest user of both the PerfCtr
and the Perfmon patches, the former being regularly installed by
vendors
On Tuesday 13 November 2007, Ingo Molnar wrote:
* David Brownell [EMAIL PROTECTED] wrote:
I speculate that either the design has changed (without fanfare),
or else that stuff is in RT kernels and has not yet gone upstream.
Well whatever. We shouldn't have to resort to
* H. Peter Anvin ([EMAIL PROTECTED]) wrote:
Mathieu Desnoyers wrote:
- Use =g constraint for char immediate value inline assembly.
=g is the same as =rmi which is inherently bogus. In your actual code
you use =r, the correct constraint is =q.
Hi Peter,
Yup, =g wasn't what I was looking
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
..
Another point is that it shifts the work from the few experienced
developers to the many users. Users (and voluntary testers) we have
many, but developer time for debugging bug reports is a
On Tue, Nov 13, 2007 at 02:12:57PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 01:47:10PM -0500, Mark Lord wrote:
Adrian Bunk wrote:
...
I did bisecting myself, and I know that it costs time and work.
But the first point is the above one that it makes otherwise nearly
On Tue, Nov 13, 2007 at 04:32:07AM -0800, David Miller wrote:
Luckily if the report being ignored isn't chaff, it will show up again
(and again and again) and this triggers a reprioritization because not
only is the bug no longer chaff, it also now got a lot of information
tagged to it so it's
Mathieu Desnoyers wrote:
- Use =g constraint for char immediate value inline assembly.
=g is the same as =rmi which is inherently bogus. In your actual code
you use =r, the correct constraint is =q.
q
Any register accessible as rl. In 32-bit mode, a, b, c, and d; in 64-bit mode, any
Network core events.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
net/core/dev.c |5 +
net/ipv4/devinet.c |5 +
net/socket.c | 18 ++
3 files changed, 28 insertions(+)
Index: linux-2.6-lttng/net/core/dev.c
This patch is a hack to make my life easier : it lessens the conflicts due to
header includes that changes between the kernel versions.
The proper way to do this is to include linux/marker.h in every file using the
markers.
NOT FOR UPSTREAM.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
Memory management core events.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
mm/filemap.c|4
mm/memory.c | 34 +-
mm/page_alloc.c |5 +
mm/page_io.c|1 +
4 files changed, 35 insertions(+), 9
Core kernel events.
*not* present in this patch because they are architecture specific :
- syscall entry/exit
- traps
- kernel thread creation
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
include/linux/module.h |1 +
kernel/exit.c |5 +
kernel/fork.c |
Hi,
I submit this instrumentation of the main kernel events using markers to the
Linux community as an RFC. This is the instrumentation LTTng (Linux Trace
Toolkit Next Generation, at http://ltt.polymtl.ca) uses.
In addition to this, I also have architecture dependent instrumentation for:
- traps
Core filesystem events markers.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: Alexander Viro [EMAIL PROTECTED]
---
fs/buffer.c |2 ++
fs/compat.c |1 +
fs/exec.c |1 +
fs/ioctl.c |2 ++
fs/open.c |2 ++
fs/read_write.c | 21
Interprocess communication, core events.
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
---
ipc/msg.c |5 -
ipc/sem.c |5 -
ipc/shm.c |5 -
3 files changed, 12 insertions(+), 3 deletions(-)
Index: linux-2.6-lttng/ipc/msg.c
On Tue, Nov 13, 2007 at 08:07:55PM +0100, Christian Kujau wrote:
I noticed that I cannot use kernel nfsd any more with 2.6.24-rc2, last
working kernel as of now is 2.6.23.1. First I was using nfsv4 but switching
to nfsv3 did not help either: exported shares can be mounted (client:
This patch adds several markers around semaphore primitives.
Along with a tracing application this patch can be useful for measuring
kernel semaphore usage and contention.
Signed-off-by: Mike Mason [EMAIL PROTECTED]
Signed-off-by: David Wilder [EMAIL PROTECTED]
Signed-off-by: Mathieu Desnoyers
Hi Mauro,
Mauro Carvalho Chehab a écrit :
Em Ter, 2007-11-06 às 18:25 +0100, Markus Hirschmann escreveu:
Hello Kernel-Developer,
Module quickcam_messenger seems to be broken (tried 2.6.18 and 2.6.22)
on 2 different NSLU2 (ARM). Picture is attached. Same kernel and module
can be used
On Tue, Nov 13, 2007 at 09:08:32AM -0500, Mark Lord wrote:
Ingo Molnar wrote:
..
This is all QA-101 that _cannot be argued against on a rational basis_,
it's just that these sorts of things have been largely ignored for
years, in favor of the all-too-easy open source means many eyeballs
On Tue, 13 Nov 2007 19:32:32 +0300 Dmitri Vorobiev [EMAIL PROTECTED] wrote:
Hi Tigran,
I found a few bugs in the BFS driver. Detailed description of the bugs as
well as the steps to reproduce the errors are given in the kernel bugzilla.
Please follow these links for more information:
On Tue, 13 Nov 2007 09:34:42 -0800 Randy Dunlap [EMAIL PROTECTED] wrote:
On Tue, 13 Nov 2007 13:50:48 +0100 Jiri Slaby wrote:
On 11/13/2007 01:15 PM, [EMAIL PROTECTED] wrote:
The mm snapshot broken-out-2007-11-13-04-14.tar.gz has been uploaded to
ERROR: nfs_put_super [fs/nfs/nfs.ko]
* H. Peter Anvin ([EMAIL PROTECTED]) wrote:
Mathieu Desnoyers wrote:
- Use =g constraint for char immediate value inline assembly.
=g is the same as =rmi which is inherently bogus. In your actual
code you use =r, the correct constraint is =q.
q
Any register accessible as rl. In 32-bit
801 - 900 of 1240 matches
Mail list logo
