* Christian Kujau ([EMAIL PROTECTED]) wrote:
> Hi there,
>
> 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:
>
On Wed, 14 Nov 2007 00:41:03 +0530 "Aneesh Kumar K.V" <[EMAIL PROTECTED]> wrote:
>
>
> 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
Hello,
I would like to enable the Magic SysRq key immediately when the linux
kernel starts to boot, not when INIT begins. So, I am familiar with the
sysctl command and /etc/sysctl.conf - but I'd like to modify these types
of kernel variables earlier in the boot process. I thought that I could,
> In the past I suggested that it might be useful to have a version of
> perfmon2 that only set up the perfmon on a global basis. That would allow
Context switch is imho the main differentiating feature of perfmon
over oprofile. Not sure it makes sense to take that one out.
I don't think the
On Tue, Nov 13, 2007 at 01:46:46PM +0100, Peter Zijlstra wrote:
>
> On Tue, 2007-11-13 at 03:18 -0800, Andrew Morton wrote:
> > On Tue, 13 Nov 2007 10:57:31 + David Howells <[EMAIL PROTECTED]> wrote:
> >
> > > SL Baur <[EMAIL PROTECTED]> wrote:
> > >
> > > > Please take the emacsism out of
* H. Peter Anvin ([EMAIL PROTECTED]) wrote:
> Mathieu Desnoyers wrote:
>> * 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
Hi,
With newer kernels HDD in my old laptop is limited to UDMA 33.
With this patch I get UDMA 100 again.
Signed-off-by: Gabriel Craciunescu <[EMAIL PROTECTED]>
---
diff --git a/drivers/ata/pata_sis.c b/drivers/ata/pata_sis.c
index 3b5be77..87546d9 100644
--- a/drivers/ata/pata_sis.c
+++
* H. Peter Anvin ([EMAIL PROTECTED]) wrote:
> 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:
* Greg KH <[EMAIL PROTECTED]>:
>
> Ok, again, I want to see the IBM people sign off on this, after
> testing on all of their machines, before I'll consider this, as
> I know the IBM acpi tables are "odd".
Who would be a good contact at IBM to get some eyes / machine
time on this?
> Also, how
> He speaks for quite a few people - they have serious need for this feature
Most likely they have serious need for a very small subset of perfmon2.
The point of my proposal was to get this very small subset in quickly.
Phil, how many of the command line options of pfmon do you
actually use? How
Hi,
With newer kernels HDD in my old laptop is limited to UDMA 33.
With this patch I get UDMA 100 again.
Signed-off-by: Gabriel Craciunescu <[EMAIL PROTECTED]>
---
diff --git a/drivers/ide/pci/sis5513.c b/drivers/ide/pci/sis5513.c
index 6b7bb53..3878224 100644
--- a/drivers/ide/pci/sis5513.c
On Tue, Nov 13, 2007 at 01:21:54PM -0700, Alex Chiang wrote:
> * Greg KH <[EMAIL PROTECTED]>:
> > On Mon, Nov 12, 2007 at 05:08:53PM -0700, Alex Chiang wrote:
> > >
> > > Recently, Matthew Wilcox sent out the following mail about
> > > PCI slots:
> > >
> > >
Amit Shah wrote:
> Glauber, are you planning on consolidating the dma_ops structure for 32- and
> 64-bit? 32-bit doesn't currently have a dma_mapping_ops structure, which
> makes paravirtualizing DMA access difficult on 32-bit.
I think it's a good idea. While I haven't worked out the details
On Tue, Nov 13, 2007 at 09:01:29AM -0800, Greg KH wrote:
>
> Also, some companies already provide userspace tools to get all of this
> information about the different slots in a system and what is where,
> from userspace, no kernel changes are needed. So, why add all this
> extra complexity to
* Greg KH <[EMAIL PROTECTED]>:
> On Mon, Nov 12, 2007 at 05:08:53PM -0700, Alex Chiang wrote:
> >
> > Recently, Matthew Wilcox sent out the following mail about
> > PCI slots:
> >
> > http://marc.info/?l=linux-pci=119432330418980=2
> >
> > The following patch series is a rough first cut at
>
Subject: x86/paravirt: revert exports to restore old behaviour
Subdividing the paravirt_ops structure caused a regression in certain
non-GPL modules which try to use mmu_ops and cpu_ops. This restores
the old behaviour, and makes it consistent with the
non-CONFIG_PARAVIRT case.
Tobias's mail:
>
On Tuesday 13 November 2007 20:59:54 Siddha, Suresh B wrote:
> Support for Intel's last branch recording to ptrace. This gives debuggers
> access to this hardware feature and allows them to show an execution trace
> of the debugged application.
Cool. Finally someone gets around to supporting this
On Tue, Nov 13, 2007 at 12:07:28PM -0800, Andrew Morton wrote:
>
> So. If what I am saying is correct then the best course of action would be
> for Stephane to help us all to understand what these features are and why
> we need them. The ideal way in which to do this is
>
> [patch] perfmon:
On Tue, Nov 13, 2007 at 01:11:02PM -0700, Matthew Wilcox wrote:
> On Tue, Nov 13, 2007 at 10:51:22AM -0800, Greg KH wrote:
> > Ok, again, I want to see the IBM people sign off on this, after testing
> > on all of their machines, before I'll consider this, as I know the IBM
> > acpi tables are
Russell King wrote:
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
Hi,
I have seen a few threads about unfixed kernel regression lately. I
strongly believe that many kernel developers and users could help
pinpointing the cause of those bugs much more efficiently by using a
tool like LTTng.
If you want to find the code I just released (both for -mm inclusion and
Adrian Bunk wrote:
On Tue, Nov 13, 2007 at 02:26:05PM -0500, Mark Lord wrote:
..
If you've been making significant updates to a driver/subsystem,
and people are reporting that it is now broken for them,
What are "significant updates"?
Sometimes one person makes one small patch and this
On Tue, 13 Nov 2007 21:09:25 +0530 Ananth N Mavinakayanahalli <[EMAIL
PROTECTED]> wrote:
> On Tue, Nov 13, 2007 at 04:00:45AM -0800, Andrew Morton wrote:
> > On Sun, 21 Oct 2007 18:09:19 +0530 Ananth N Mavinakayanahalli <[EMAIL
> > PROTECTED]> wrote:
> >
> > > Move kprobes examples from
On Tue, Nov 13, 2007 at 07:32:19PM +, Russell King wrote:
>...
> There's another issue I want to raise concerning bugzilla. We have the
> classic case of "not enough people reading bugzilla bugs" - which is one
> of the biggest problems with bugzilla. Virtually no one in the ARM
> community
On Tue, Nov 13, 2007 at 10:51:22AM -0800, Greg KH wrote:
> Ok, again, I want to see the IBM people sign off on this, after testing
> on all of their machines, before I'll consider this, as I know the IBM
> acpi tables are "odd".
That seems a little higher standard than patches are normally held
On Tue, 13 Nov 2007 10:59:24 -0800 Greg KH <[EMAIL PROTECTED]> wrote:
> 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
Theodore Tso wrote:
>
> Heh. I hadn't enabled CONFIG_BCM43XX_DEBUG myself, but I just changed
> it for my next kernel build. This is a slightly different issue,
> which is that sometimes _DEBUG options shouldn't be turned on by
> default (because they really trash performance and bloat log
Patrick McHardy wrote:
> Kok, Auke wrote:
>> Patrick McHardy wrote:
>>
>>> I already posted a patch for this, not sure what happened to it.
>>> Auke, any news on merging the secondary unicast address support?
>>
>> I dropped the ball on that one. Care to resend it and send me one for
>> e1000e as
On Tue, Nov 13, 2007 at 07:46:49PM +, Russell King wrote:
> On Tue, Nov 13, 2007 at 08:30:35PM +0100, Adrian Bunk wrote:
> > There is this silly limit that noone can work more than 168 hours per
> > week on the Linux kernel, and some kernel developers seem to take the
> > liberty of spending
Support for Intel's last branch recording to ptrace. This gives debuggers
access to this hardware feature and allows them to show an execution trace
of the debugged application.
Last branch recording (see section 18.5 in the Intel 64 and IA-32
Architectures Software Developer's Manual) allows
On Tue, Nov 13, 2007 at 01:56:46PM -0600, Linas Vepstas wrote:
> On Mon, Nov 12, 2007 at 05:14:47PM -0700, Alex Chiang wrote:
> > +/* pci_slot represents a physical slot */
> > +struct pci_slot {
> > + struct pci_bus *bus;/* The bus this slot is on */
> > + struct pci_slot *next;
On Tue, 13 Nov 2007, Andrew Morton wrote:
I think that we're fairly good about working the regressions in
Adrian/Michal/Rafael's lists but once Linus releases 2.6.x we tend to let
the unsolved ones slide, and we don't pay as much attention to the
regressions which 2.6.x testers report.
Can't
On Tue, Nov 13, 2007 at 02:26:05PM -0500, Mark Lord wrote:
> 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
Mathieu Desnoyers wrote:
* 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
Hi there,
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: 2.6-git/powerpc32, nfs-common-1.1.1~git-20070709-3ubuntu1), but
On Tue, 13 Nov 2007 14:34:19 +0100 "Thomas Lindroth" <[EMAIL PROTECTED]> wrote:
> >
> > On Sun, 11 Nov 2007 22:46:43 + Alan Cox <[EMAIL PROTECTED]>
> > wrote:
> >
> > > > [PATCH] pata_amd/pata_via: de-couple programming of PIO/MWDMA and UDMA
> > timings
> > > >
> > > > * Don't program UDMA
On Mon, Nov 12, 2007 at 05:14:47PM -0700, Alex Chiang wrote:
> +/* pci_slot represents a physical slot */
> +struct pci_slot {
> + struct pci_bus *bus;/* The bus this slot is on */
> + struct pci_slot *next; /* Next slot on this bus */
> + struct hotplug_slot
On Tue, Nov 13, 2007 at 01:48:15PM -0600, Linas Vepstas wrote:
> On Mon, Nov 12, 2007 at 05:13:36PM -0700, Alex Chiang wrote:
> > + slot->name = kmalloc(8, GFP_KERNEL);
> > + sprintf(slot->name, "fake%d", count++);
>
> Please use snprintf to avoid buffer overruns!
Or, since kmalloc can
On Tue, Nov 13, 2007 at 08:30:35PM +0100, Adrian Bunk wrote:
> There is this silly limit that noone can work more than 168 hours per
> week on the Linux kernel, and some kernel developers seem to take the
> liberty of spending even less time on kernel development...
That limit of 168 hours
On Mon, Nov 12, 2007 at 05:13:36PM -0700, Alex Chiang wrote:
> + slot->name = kmalloc(8, GFP_KERNEL);
> + sprintf(slot->name, "fake%d", count++);
Please use snprintf to avoid buffer overruns!
--linas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
* 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
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
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"
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
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
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
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:
>
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
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
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 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
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
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
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
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
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
* 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
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
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
> [...]
> 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
* 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
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.
..
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
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':
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
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
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.
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
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
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
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
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
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
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]>
---
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
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
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.
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
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
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: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
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
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
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]
---
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]
---
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]
---
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
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
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
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:
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(-)
301 - 400 of 1240 matches
Mail list logo
