> +config IMMEDIATE
> + default y if !DISABLE_IMMEDIATE
It's still unclear to me why DISABLE_IMMEDIATE is needed. It would
be better to make it just the default.
> +config DISABLE_IMMEDIATE
> + default y if EMBEDDED
> + bool "Disable immediate values" if EMBEDDED
> + depends on X8
On Wed, Sep 05, 2007 at 01:00:15PM -0400, Luis R. Rodriguez wrote:
> On 9/5/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > On Wednesday 05 September 2007, Reyk Floeter wrote:
> > > I'm the author of the free hardware driver layer for wireless Atheros
> > > devices in OpenBSD, also known as "Open
In article <[EMAIL PROTECTED]> you wrote:
> So you can't draw any relationships between "Protect the end-user"
> with "Protect the device FROM the end-user", the former can be done
> very reliably to whatever level of risk-reduction you need and the
> latter can't practically be done at all.
El Fri, Sep 07, 2007 at 12:08:34AM +0200 Oleg Verych ha dit:
> * Thu, 6 Sep 2007 23:18:15 +0200
>
> []
> > @@ -184,7 +184,7 @@ struct u132_ring {
> > struct u132 {
>
> Subject: [PATCH 1/2] ELAN U132 Host Controller Driver: convert sw_lock to
> mutex
> []
> > struct list_head u132_list
On Tue, 2007-09-04 at 13:57 +0800, Bryan Wu wrote:
> This is the driver for latest Blackfin on-chip nand flash controller
>
> - use nand_chip and mtd_info common nand driver interface
> - provide both PIO and dma operation
> - compiled with ezkit bf548 configuration
> - use hardware 1-bit ECC
On Sep 07, 2007, at 01:14:09, Trond Myklebust wrote:
On Thu, 2007-09-06 at 20:56 -0400, Kyle Moffett wrote:
Umm, I did say "encrypt the root filesystem", didn't I? Booting
my laptops this way follows this procedure:
1) Enter BIOS boot menu
2) Insert /boot CDROM
3) Select the "CDROM"
Hi,
Any filesystem namespace unification solution (Union Mount, Unionfs) needs to
provide a unified or merged view of directory contents. Typically this is
done by reading the directory entries of all the union'ed layers (starting
from the top and working downwards) and merging the result by elimi
I've received two oopses now from my kernel while running
the 2.6.22 series. The first was with 2.6.22.1 back in July and
the second which happened just within the last day is 2.6.22.5.
They both appear to be the same bug and I don't think it's
hardware related. I'm attaching the entries
On Thu, 2007-09-06 at 20:56 -0400, Kyle Moffett wrote:
> On Sep 06, 2007, at 19:35:14, Trond Myklebust wrote:
> > On Thu, 2007-09-06 at 19:30 -0400, Kyle Moffett wrote:
> >> Actually, that's a fairly simple problem (barring disassembling
> >> the system and attaching a hardware debugger). You en
[EMAIL PROTECTED] wrote:
On Thu, 06 Sep 2007 16:37:37 PDT, Randy Dunlap said:
Thanks. I look forward to the explanation of Reviewed-by, what it
means, and how it differs from Acked-by.
As long as you're at it, the only tag *I* seem to need is 'Tested-By:' :)
Yep, and that's a good one IMO
On Thu, 06 Sep 2007 16:37:37 PDT, Randy Dunlap said:
> Thanks. I look forward to the explanation of Reviewed-by, what it
> means, and how it differs from Acked-by.
As long as you're at it, the only tag *I* seem to need is 'Tested-By:' :)
pgppNJ0dzigyz.pgp
Description: PGP signature
As the block/blktrace.c and kernel/sched.c are common (core) files for
all architectures, an access function has been defined for referencing
the cpu_sibling_map array.
Signed-off-by: Mike Travis <[EMAIL PROTECTED]>
---
arch/ia64/Kconfig|1 -
block/blktrace.c |2 +-
includ
Convert cpu_sibling_map to a per_cpu cpumask_t array for the ppc64
architecture.
Note: these changes have not been built nor tested.
Note: I also don't know if these changes are particularly
relevant for the ppc64 architecture.
Signed-off-by: Mike Travis <[EMAIL PROTECTED]>
---
arch/powerpc/ker
Convert cpu_sibling_map to a per_cpu cpumask_t array for the ia64
architecture.
There was one access to cpu_sibling_map before the per_cpu data
area was created, so that step was moved to after the per_cpu
area is setup.
Note also that references to cpu_sibling_map have been changed
to use the cp
Since the core kernel routines need to reference cpu_sibling_map,
whether it be a static array or a per_cpu data variable, an access
function has been defined.
In addition, changes have been made to the ia64 and ppc64 arch's to
move the cpu_sibling_map from a static cpumask_t array [NR_CPUS] to
b
On Wed, 05 Sep 2007 04:48:05 MDT, Sean Robert McGuffee said:
> machine. For those who make the argument that someone logged in as root
> might break the machine by doing something they shouldn't, I would say
> it's already broken without being root.
Hint 1: If you're not smart enough to figure
On Thu, 06 Sep 2007 14:53:01 +0100
Mel Gorman <[EMAIL PROTECTED]> wrote:
> Does it really matter as they routinely do not take zone->lru_lock
> either? pages_min, pages_low and pages_high are currently examined on a
> regular basis by zone_watermark_ok() without any locks held in the page
> alloca
On Thursday 06 September 2007 17:29, Vladimir Shebordaev wrote:
> This patch fixes a nasty typo in usbtouchscreen driver.
>
> The typo is inherited from the original mtouchusb. It
> used to make the input subsytem to incorrectly
> report the physical device ids to userspace that in turn
> is much
On Thu, 2007-09-06 at 05:57 -0600, Matthew Wilcox wrote:
> On Thu, Sep 06, 2007 at 01:35:08PM +0800, Shaohua Li wrote:
> > PCIE 'Enable No Snoop' bit is set by default per PCIE spec, but OS
> > assumes PCI DMA is snooped, which is legacy PCI device does. Enabling no
> > snoop might cause potential
On 9/6/07, Manuel Reimer <[EMAIL PROTECTED]> wrote:
> Andreas Schwab wrote:
> >> As I would prefer to use the USB device information (idVendor, idProduct)
> >> to detect the device, I also tried this one:
> >>
> >> ATTRS{idVendor}=="0dda", ATTRS{idProduct}=="2005", SUBSYSTEM=="scsi",
> >> ACTION=="
Hello,
Mark Lord wrote:
> I reported a very similar bug back a few releases ago.
> Anyone who wants to try it themselves, can do this with hdparm-7.7 (from
> sourceforge):
>
>hdparm --drq-hsm-error /dev/sda
>
> Whether or not it hangs the machine does depend upon exactly which SATA
> LLD is
Bryan Woods wrote:
> The full dmesg and hdparm -I command output are attached.
>
> I have received word from the vendor that the Stardom 2611 will do
> RAID0 or 1 under windows, but only RAID1 under Linux. (Their manual
> said it worked with Linux but failed to mention the RAID mode
> restriction
On Sep 06, 2007, at 19:35:14, Trond Myklebust wrote:
On Thu, 2007-09-06 at 19:30 -0400, Kyle Moffett wrote:
Actually, that's a fairly simple problem (barring disassembling
the system and attaching a hardware debugger). You encrypt the
root filesystem and require a password to boot (See: LUKS
On Mon 2007-09-03 04:58:58, Jeff Garzik wrote:
> David Schwartz wrote:
> >Either license can grant you the right to distribute
> >it, but how you get the
> >rights to distribute has *NO* effect on the recipient.
> >They receive a lawful
> >copy and any rights the original author grants them
> >u
H. Peter Anvin ([EMAIL PROTECTED]) said:
> Hmmm...
>
> Personally I'd suggest making it the default unless overridden in
> /etc/sysctl.conf. My second preference would be a command-line option, not
> a compile-time default.
>
> This is 2007, after all, and it seems Unicode should be the default
On Thu, 06 Sep 2007 16:07:36 -0400 Mathieu Desnoyers wrote:
> Here is some documentation explaining what is/how to use the Linux
> Kernel Markers.
> ---
>
> Documentation/marker.txt | 257
> +++
> 1 file changed, 257 insertions(+)
>
> Index: linux-2
On Thu, 06 Sep 2007 16:07:35 -0400 Mathieu Desnoyers wrote:
[snip]
> This patch:
>
> Add Kconfig menus for the marker code.
>
> [EMAIL PROTECTED]: Never ever select MODULES]
> Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
> Reviewed-by: Christoph Hellwig <[EMAIL PROTECTED]>
> Reviewed-by
On Thu, 6 Sep 2007 16:04:29 -0700 Andrew Morton wrote:
> > On Thu, 6 Sep 2007 16:00:01 -0700 Randy Dunlap <[EMAIL PROTECTED]> wrote:
> > On Thu, 06 Sep 2007 16:07:34 -0400 Mathieu Desnoyers wrote:
> >
> > > Changelog:
> > > - markers_mutex now nests inside module_mutex rather than the opposite.
>
On Sep 06, 2007, at 11:06:16, J. Bruce Fields wrote:
On Thu, Sep 06, 2007 at 01:44:05PM +0530, Satyam Sharma wrote:
Like Trond said, there are very high number of ways in which
privileged userspace can compromise a running kernel if it really
wants to do that, root-is-God has always been *the
On Thu, 6 Sep 2007, Michael Kerrisk wrote:
> You are asserting this in the face of two previous APIs designed
> by people who (at least in the case of POSIX timers) probably
> thoroughly examined and discussed existing APIs and practice.
You really think that. Uhmm, ok.
> This function is *n
On Thu, 2007-09-06 at 19:30 -0400, Kyle Moffett wrote:
> On Sep 06, 2007, at 11:06:16, J. Bruce Fields wrote:
> > On Thu, Sep 06, 2007 at 01:44:05PM +0530, Satyam Sharma wrote:
> >> Like Trond said, there are very high number of ways in which
> >> privileged userspace can compromise a running ker
On Fri, 2007-09-07 at 01:21 +0200, Trond Myklebust wrote:
> On Thu, 2007-09-06 at 11:11 -0400, J. Bruce Fields wrote:
> > On Thu, Sep 06, 2007 at 01:59:50PM +0530, Satyam Sharma wrote:
> > > Oh and btw, note that we're talking of the (lack of) security of a
> > > "running kernel" here -- because ac
On Thu, 2007-09-06 at 12:55 -0700, Fernando Lopez-Lezcano wrote:
> On Thu, 2007-09-06 at 11:42 -0700, Fernando Lopez-Lezcano wrote:
> > On Tue, 2007-09-04 at 17:15 -0700, Daniel Walker wrote:
> > > On Tue, 2007-09-04 at 17:12 -0700, Fernando Lopez-Lezcano wrote:
> > > > Hi Ingo... I'm getting repor
On Thu, 2007-09-06 at 11:11 -0400, J. Bruce Fields wrote:
> On Thu, Sep 06, 2007 at 01:59:50PM +0530, Satyam Sharma wrote:
> > Oh and btw, note that we're talking of the (lack of) security of a
> > "running kernel" here -- because across reboots, there is /really/
> > *absolutely* no such thing as
> On Thu, 6 Sep 2007 16:00:01 -0700 Randy Dunlap <[EMAIL PROTECTED]> wrote:
> On Thu, 06 Sep 2007 16:07:34 -0400 Mathieu Desnoyers wrote:
>
> > Changelog:
> > - markers_mutex now nests inside module_mutex rather than the opposite.
> >
> > Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
> > R
> On Thu, 6 Sep 2007 14:40:11 -0400 Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
> Guess what, another one ;)
>
>
> /opt/crosstool/gcc-4.1.1-glibc-2.3.6/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-gcc
> -m32 -Wp,-MD,arch/ppc/kernel/.asm-offsets.s.d -nostdinc -isystem
> /o
On Thu, 06 Sep 2007 16:07:34 -0400 Mathieu Desnoyers wrote:
> Changelog:
> - markers_mutex now nests inside module_mutex rather than the opposite.
>
> Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
> Reviewed-by: Christoph Hellwig <[EMAIL PROTECTED]>
> Reviewed-by: Rusty Russell <[EMAIL PRO
Andrew Morton wrote:
On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <[EMAIL PROTECTED]> wrote:
Andrew Morton wrote:
(What happened to the other stuff I said?)
Mlock can cause the problem too. As for all_unreclaimable,
it is ignored when priority == DEF_PRIORITY, balance_pgdat
always seems t
On Fri, Sep 07, 2007 at 12:01:56AM +0200, Oleg Verych wrote:
>...
> > And code review and Denys' patch have cumulative effects since his patch
> > results in improvements that can't be resonably done other than at
> > the ld and/or gcc level.
>
> I was talking about introducing such things in de
tir, 04 09 2007 kl. 23:06 +0200, skrev Jens Axboe:
> On Tue, Sep 04 2007, Simon Holm Thøgersen wrote:
> > tir, 04 09 2007 kl. 13:06 +0200, skrev Jens Axboe:
> > > On Tue, Sep 04 2007, Micah Gruber wrote:
> > > > This patch fixes a potential null dereference bug where we dereference
> > > > us befo
> On Thu, 06 Sep 2007 12:38:13 -0400 Rik van Riel <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
>
(What happened to the other stuff I said?)
> > I guess for a very small upper zone and a very large lower zone this could
> > still put the scan balancing out of whack, fixable by a smarter vers
On Thu, Sep 06, 2007 at 11:59:41AM +0100, Denys Vlasenko wrote:
> On Wednesday 05 September 2007 21:07, Sam Ravnborg wrote:
> > On Wed, Sep 05, 2007 at 02:47:00PM +0100, Denys Vlasenko wrote:
> > > On Wednesday 05 September 2007 14:43, Denys Vlasenko wrote:
> > > > These patches fix section names a
On Thu, Sep 06, 2007 at 11:55:52AM +0100, Denys Vlasenko wrote:
>
> > Doing a normal kernel build will link vmlinux three or four times.
> > If we introduce --gc-sections we should add a preparational link of
> > vmlinux where we use --gc-sections and skip it for the rest of the links
> > assuming
On Monday 03 September 2007 12:01:17 Shahbaz Khan wrote:
> Hi,
>
> I am searching for a linux kernel, network and system programming
> related mailing list for a newbie to intermediate level programmer.
> Kernel newbie seems to be not working. Anyone know of others?
>
The Kernel Newbies list may
# ls -li
total 0
4026532007 -r--r--r-- 1 root root 0 Sep 6 18:18 nvram
4026532067 -r--r--r-- 1 root root 0 Sep 6 18:18 rtc
4026532067 -r--r--r-- 1 root root 0 Sep 6 18:18 rtc
4026532056 -rw-r--r-- 1 root root 0 Sep 6 18:18 snd-page-alloc
kernel 2.6.22.6 on a Dell Precision 390:
# CONFIG_RTC i
06 September 2007 Michal Piotrowski wrote:
[..]
> > CPU 0: Machine Check Exception: 0004
> > Bank 4: b2070f0f
> > Kernel panic - not syncing: CPU context corrupt
>
> It is a hardware problem.
>
> You may want to use mcelog ftp://ftp.x86-64.org/pub/linux/tools/mcelog/
Tried this
From: Vladimir Shebordaev <[EMAIL PROTECTED]>
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g. XInput ho
From: Vladimir Shebordaev <[EMAIL PROTECTED]>
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g. XInput ho
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g. XInput hotplug facilities in
setups with multiple identi
Andreas Schwab wrote:
Manuel Reimer <[EMAIL PROTECTED]> writes:
For me, this looks like a bug, or am I wrong?
It's a feature. It's documented.
man udev says:
| The name of the device matched while searching the devpath upwards
| for SUBSYSTEMS, KERNELS, DRIVERS and ATTRS.
What exactly doe
It is ok to call prefetch() function with NULL argument, as specifically
commented in include/linux/prefetch.h. But in standard C, it is invalid to
dereference NULL pointer (see C99 standard 6.5.3.2 paragraph 4 and note #84).
Newer gcc versions (4.3 and above) will use that to conclude that "x"
a
* Thu, 6 Sep 2007 23:18:15 +0200
[]
> @@ -184,7 +184,7 @@ struct u132_ring {
> struct u132 {
Subject: [PATCH 1/2] ELAN U132 Host Controller Driver: convert sw_lock to mutex
[]
> struct list_head u132_list;
> -struct semaphore sw_lock;
> +struct mutex sw_lock;
>
On Thu, 2007-09-06 at 17:25 +0200, Takashi Iwai wrote:
> At Thu, 06 Sep 2007 17:09:50 +0200,
> Romano Giannetti wrote:
> >
> >
> > Just one hand up: I haven't tested the patch pointed to by Andrew, will
> > do asap, but it seems that contains the changes from
> >
> > https://bugtrack.alsa-project
Manuel Reimer <[EMAIL PROTECTED]> writes:
> For me, this looks like a bug, or am I wrong?
It's a feature. It's documented.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756
* Thu, 6 Sep 2007 23:19:55 +0200
>
> On Thu, Sep 06, 2007 at 11:16:15PM +0200, Oleg Verych wrote:
>> * Thu, 6 Sep 2007 22:39:31 +0200
>>
>> []
>> >> > His patch improves the build process.
>> >>
>> >> I would like to know timing, btw. Size, especially shown 1%, doesn't
>> >> matter if link time i
On Thu, Sep 06, 2007 at 03:25:55PM +0530, Satyam Sharma wrote:
> This is a GCC bug (regression, actually, as you've found out) -- no two
> ways about it. Although different from the kind Jeff mentioned couple days
> back -- that was about wising GCC up to false positives and /not/ emitting
> warn
This patch fixes a nasty typo in usbtouchscreen driver.
The typo is inherited from the original mtouchusb. It
used to make the input subsytem to incorrectly
report the physical device ids to userspace that in turn
is much confusing for, e.g. XInput hotplug facilities in
setups with multiple identi
On Thu, 06 Sep 2007 16:02:36 -0400 Mathieu Desnoyers wrote:
> Documentation/immediate.txt | 232
>
> 1 file changed, 232 insertions(+)
>
> Index: linux-2.6-lttng/Documentation/immediate.txt
> =
The ELAN U132 Host Controller Driver uses the semaphore scheduler_lock
as mutex. Use the mutex API instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/usb/host/u132-hcd.c b/drivers/usb/host/u132-hcd.c
index b88eb3c..e22 100644
--- a
On Thu, Sep 06, 2007 at 11:16:15PM +0200, Oleg Verych wrote:
> * Thu, 6 Sep 2007 22:39:31 +0200
>
> []
> >> > His patch improves the build process.
> >>
> >> I would like to know timing, btw. Size, especially shown 1%, doesn't
> >> matter if link time increased dramatically. `Allyes' config, when
This patchset converts sw_lock and scheduler_lock in the ELAN U132
Host Controller Driver from semaphores to the mutex API
--
Matthias Kaehlcke
Linux Application Developer
Barcelona
La libertad es como la mañana. Hay quienes esperan dormidos a que
llegue, pero hay quienes desvelan y cam
The ELAN U132 Host Controller Driver uses the semaphore sw_lock as
mutex. Use the mutex API instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/usb/host/u132-hcd.c b/drivers/usb/host/u132-hcd.c
index b88eb3c..1201ca4 100644
--- a/driver
Mathieu,
# CONFIG_INET_LRO is not set
The in-kernel driver now depends on CONFIG_INET_LRO.
The kconfig needs to be changed to reflect this, and we will submit a patch.
In the meantime, you could alternatively use the Myri10GE 1.3.1 driver
from the download page:
http://www.myri.com/scs/
* Thu, 6 Sep 2007 22:39:31 +0200
[]
>> > His patch improves the build process.
>>
>> I would like to know timing, btw. Size, especially shown 1%, doesn't
>> matter if link time increased dramatically. `Allyes' config, when i
>> had fast and rammish machine was terrible thing (last winter). If 32
Jan Engelhardt wrote:
On Sep 4 2007 13:53, Guilherme Vilela wrote:
I'm tryng to mount a nfs file system with the option async and run a
program that writes to the file system. The problem is that the
program keep writing even when the file system is full.
man 5 exports
async This
Andreas Schwab wrote:
As I would prefer to use the USB device information (idVendor, idProduct)
to detect the device, I also tried this one:
ATTRS{idVendor}=="0dda", ATTRS{idProduct}=="2005", SUBSYSTEM=="scsi",
ACTION=="add", PROGRAM+="/usr/bin/test.sh %b %p"
Now this version returns the USB de
On Thu, 6 Sep 2007 16:05:37 -0400 Mathieu Desnoyers wrote:
> Scheduler Profiling - Use Immediate Values
>
> Use immediate values with lower d-cache hit in optimized version as a
> condition for scheduler profiling call.
>
> Depends on the Immediate values patches, applies to 2.6.23-rc4-mm1.
>
>
From: Bernhard Walle <[EMAIL PROTECTED]>
Date: Thu, 6 Sep 2007 22:01:52 +0200
> [PATCH] Fix config requirements of IPv6
>
> net/ipv6/inet6_connection_sock.c in function __inet6_csk_dst_store() requires
> flow_cache_genid which is defined in net/core/flow.c which is compiled when
> CONFIG_XFRM is
From: David Miller <[EMAIL PROTECTED]>
Date: Thu, 06 Sep 2007 13:40:38 -0700 (PDT)
> From: Mathieu Desnoyers <[EMAIL PROTECTED]>
> Date: Thu, 6 Sep 2007 15:37:51 -0400
>
> > I got a link error on myri10ge when building 2.6.23-rc4-mm1 on x86_64 :
> >
> > ERROR: "lro_flush_all" [drivers/net/myri10
Here is the first stage of a port of blktrace to the Linux Kernel Markers. The
advantage of this port is that it minimizes the impact on the running when
blktrace is not active.
A few remarks : this patch has the positive effect of removing some code
from the block io tracing hot paths, minimizing
[PATCH] Fix config requirements of IPv6
net/ipv6/inet6_connection_sock.c in function __inet6_csk_dst_store() requires
flow_cache_genid which is defined in net/core/flow.c which is compiled when
CONFIG_XFRM is set.
This patch expresses that dependency.
Signed-off-by: Bernhard Walle <[EMAIL PROTE
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/i386/mm/init.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
Index: linux-
From: Mathieu Desnoyers <[EMAIL PROTECTED]>
Date: Thu, 6 Sep 2007 15:37:51 -0400
> I got a link error on myri10ge when building 2.6.23-rc4-mm1 on x86_64 :
>
> ERROR: "lro_flush_all" [drivers/net/myri10ge/myri10ge.ko] undefined!
> ERROR: "lro_receive_frags" [drivers/net/myri10ge/myri10ge.ko] undef
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_set(), which is basically a memset-li
Make kprobes use text_set instead of text_poke.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Andi Kleen <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
arch/x86_64/kernel/kprobes.c |4 ++--
1 file changed, 2 insertion
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]>
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
ker
Fix a bad call to flush_icache_range(). The second parameter is the end address
of the range, not the length.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Christoph Hellwig <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/immediate.c |4 ++--
1 file changed, 2 insertions(+), 2 deletion
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 of
While porting my code from an older markers version I noticed the
marker callbacks have grown a void *private argument. Add it to
the documentation aswell.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
Documentation/marker.txt |
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
Documentation/immediate.txt | 232
1 file changed, 232 insertions(+)
Index: linux-2.6-lttng/Documentation/immediate.txt
===
--- /d
Andrew, any chance to get this into -mm ASAP so we can have it in
2.6.24?
Just in case anyone wonders what this is usefulfor I've ported my
hacking spu tracing code to it, and if markers get in I'd push a cleaned
up version of this in the tree of the benefit of everyone trying to
follow what's goi
On Thu, Sep 06, 2007 at 10:43:49PM +0200, Oleg Verych wrote:
> On Thu, Sep 06, 2007 at 02:21:43PM +0200, Adrian Bunk wrote:
> []
> > > You've did a tool. Documenting this tool to have it available for
> > > testers/janitors/maintainers is a better way, than to have all that
> > > opinions/problems
On Fri, 31 August 2007 18:41:07 -0700, Christoph Lameter wrote:
>
> The trouble with this patchset is that it is difficult to validate.
> Activities are only performed when special load situations are encountered.
> Are there any tests that could give meaningful information about
> the effectivene
On Thu, Sep 06, 2007 at 02:21:43PM +0200, Adrian Bunk wrote:
[]
> > You've did a tool. Documenting this tool to have it available for
> > testers/janitors/maintainers is a better way, than to have all that
> > opinions/problems with merging-to-mainline.
>
> There is no problem with his patch.
>
>
On Thu, 6 Sep 2007 15:46:32 -0400 Mathieu Desnoyers wrote:
> Hi Peter,
>
> I have seen the following warning on the recent -mm kernels when
> compiling a i386 kernel:
>
> scripts/mod/modpost -o
> /home/compudj/git/morestable/linux-2.6-lttng/Module.symversvmlinux.o
> WARNING: vmlinux.o(.
TROLL or incredible ignoramus -> do not feed.
{^_^}
- Original Message -
From: "Sean Robert McGuffee" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, 2007, September 05 03:48
Subject: AUTO LOGIN BUG
Dear whoever is in charge of writing fedora core 7,
The auto login is a wonderful feature
Hi Andrew,
Some people asdked me for a tarball easy to apply of my patches. I give
a link to it for those interested.
http://ltt.polymtl.ca/markers/markers-patches-for-2.6.23-rc4-mm1-06-09-2007.tar.bz2
Mathieu
It comes along with this series file:
kprobes-use-mutex-for-insn-pages.patch
kprobe
With the increasing complexity of today's user-space application and the wide
deployment of SMP systems, the users need an increasing understanding of the
behavior and performance of a system across multiple processes/different
execution contexts/multiple CPUs. In applications such as large cluste
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
Reviewed-by: Christoph Hellwig <[EMAIL PROTECTED]>
Reviewed-by: "Frank Ch. Eigler" <[EMAIL PROTECTED]>
---
Documentation/marker.txt | 257 +
The marker activation functions sits in kernel/marker.c. A hash table is used
to keep track of the registered probes and armed markers, so the markers within
a newly loaded module that should be active can be activated at module load
time.
marker_query has been removed. marker_get_first, marker_ge
Hi Andrew,
Here are the Linux Kernel Markers for 2.6.23-rc4-mm1. They depend on the sorted
module list and on the immediate values.
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE
Hi Andrew,
Here is the updated version of the patchset for 2.6.23-rc4-mm1. It should be
ready to apply. More users (other than module.c and the markers), such as
kallsyms, may also come in a near future.
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Mon
Add support for sorted list in seq_file. It aims at changing the way
/proc/modules and kallsyms iterates on the module list to remove a race between
module unload and module/symbol listing.
The list is sorted by ascending list_head pointer address.
Changelog:
When reading the data by small chunk
A race that appears both in /proc/modules and in kallsyms: if, between the
seq file reads, the process is put to sleep and at this moment a module is
or removed from the module list, the listing will skip an amount of
modules/symbols corresponding to the amount of elements present in the unloaded
m
Scheduler Profiling - Use Immediate Values
Use immediate values with lower d-cache hit in optimized version as a
condition for scheduler profiling call.
Depends on the Immediate values patches, applies to 2.6.23-rc4-mm1.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c
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" su
i386 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
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]>
CC: Christoph Hellwig <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
CC: [EMAIL
PowerPC optimization of the immediate values which uses a li instruction,
patched with an immediate value.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Christoph Hellwig <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/Makefile|1
arch/powerpc/kernel/immediate.c | 103 +++
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()
1 - 100 of 253 matches
Mail list logo
