A lot of Ubuntu users have noticed troubles with Wacom Serial Tablet
devices (mainly builtin units in Toshiba tablet PCs) refusing to
properly return from ACPI Suspend or Hibernate. See the bug report at:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152187
Tom Jaeger there
>>> Eric W. Biederman <[EMAIL PROTECTED]> 21.12.07 00:05 >>>
>"Jan Beulich" <[EMAIL PROTECTED]> writes:
>
>> Remains the question whether it is intended that many, perhaps even
>> large, tables are compiled in without ever having a chance to get used,
>> i.e. whether there shouldn't #ifdef
On Thu, 2007-12-20 at 19:14 +0100, Hemmann, Volker Armin wrote:
> It is just.. I could be the hardware - but I should have seen the
> same 'problem' with earlier kernels - and the 'almost daily oops' only
> started with 2.6.23.
Nonetheless, the oopsen _suggest_ hardware. If it were my box,
This patch adds a file in proc file system to access the loaded
kexec_image, which may contains the memory image of kexeced
system. This can be used to:
- Communicate between original kernel and kexeced kernel through write
to some pages in original kernel.
- Communicate between original
Thanks for catching this!
>>> Dave Jones <[EMAIL PROTECTED]> 21.12.07 03:30 >>>
On Thu, Dec 20, 2007 at 04:14:05PM -0700, Eric W. Biederman wrote:
> Remains the question whether it is intended that many, perhaps even
> large, tables are compiled in without ever having a chance to get used,
>
This patch implements the functionality of jumping between the kexeced
kernel and the original kernel.
To support jumping between two kernels, before jumping to (executing)
the new kernel and jumping back to the original kernel, the devices
are put into quiescent state, and the state of devices
This patch adds writing support for /dev/oldmem. This can be used to
- Communicate between original kernel and kexeced kernel through write
to some pages in original kernel.
- Restore the memory contents of hibernated system in kexec based
hibernation.
Signed-off-by: Huang Ying <[EMAIL
This patchset provides an enhancement to kexec/kdump. It implements
the following features:
- Backup/restore memory used both by the original kernel and the
kexeced kernel.
- Jumping between the original kernel and the kexeced kernel.
- Read/write memory image of the kexeced kernel in the
>Yes, but why export variables? Wouldn't it be better to export
>an API?
>
>That simplifies the callers (they all pass "current" as task
>and "task_notifier_list" as arguments).
>
>It also prevents exposing internal variables (notifier lists
>ARE internal variables) to modules.
>
>What do you
Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
control the wire and the GPIO pin can be specified using platform data
similar to i2c-gpio. The driver was tested with AT91SAM9260 + DS2401.
Signed-off-by: Ville Syrjala <[EMAIL PROTECTED]>
---
Documentation/w1/masters/00-INDEX
On Thu, Dec 20, 2007 at 10:59:20PM -0800, Srinivas Kommu wrote:
> It seems this kind of a deadlock can happen with any kernel lock, not
> just files_lock. What's the driver's mistake here? Is it wrong to call
> remove_proc_entry() while holding another lock? What is the right thing
> to do?
On Thu, Dec 20, 2007 at 03:58:16AM -0800, Roland McGrath wrote:
> +obj-$(CONFIG_PPC64) += ../../../fs/compat_binfmt_elf.o
Building files from another directory is nasty. Please add a
CONFIG_BINFMT_COMPAT_ELF so we can simply build it in fs/
--
To unsubscribe from this list: send the
On Thu, Dec 20, 2007 at 03:55:51AM -0800, Roland McGrath wrote:
> This adds a generic definition of compat_sys_ptrace that calls
> compat_arch_ptrace, parallel to sys_ptrace/arch_ptrace. Some
> machines needing this already define a function by that name.
> The new generic function is defined
I have a driver that needs to be SMP-safe. It also has some code hooking
into the net_rx_action softirq. So it takes a spinlock and disables the
local bottom-half around its critical sections:
spin_lock_bh(_lock). Now, I'm facing a deadlock under a
particular sequence involving the files_lock:
On Thu, Dec 20, 2007 at 03:53:57AM -0800, Roland McGrath wrote:
> +/*
> + * User-mode machine state access
> + *
> + * Copyright (C) 2007 Red Hat, Inc. All rights reserved.
> + *
> + * This copyrighted material is made available to anyone wishing to use,
> + * modify, copy, or redistribute it
On Fri, 21 Dec 2007 00:58:19 -0500 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On further investigation, "cat /proc/iomem" does not
On Thu, 2007-12-20 at 18:30 -0800, Andrew Morton wrote:
> On Wed, 12 Dec 2007 15:38:26 -0800 Harvey Harrison <[EMAIL PROTECTED]> wrote:
>
> > Andrew, I'm not sure who is best to hit with these final dribs and
> > drabs removing fastcall. Once all of these have hit Linus' tree
> > I will send a
Resending... Curse GMail's HTML messages!
On Dec 21, 2007 12:58 AM, Miles Lane <[EMAIL PROTECTED]> wrote:
>
> On Dec 20, 2007 12:32 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <[EMAIL PROTECTED]> wrote:
> >
> > > On further investigation, "cat
On Dec 20 2007 23:05, Ilpo Järvinen wrote:
>>
>> Given the fact that I've had this problem for so long, over a variety
>> of networking hardware vendors and colo-facilities, this really sounds
>> good to me. It will be challenging for me to justify a kernel core
>> dump, but a simple patch to
> > ===
> > --- linux-2.6-lttng.orig/kernel/kprobes.c 2007-12-12
> > 18:10:32.0 -0500
> > +++ linux-2.6-lttng/kernel/kprobes.c2007-12-12
> > 18:10:34.0 -0500
> > @@ -644,7 +644,9 @@ valid_p:
> >
I am trying to do an i2c block read using a call like
rc = i2c_smbus_xfer(g_i2c_adp, buf[0], 0x0,
I2C_SMBUS_READ, 0x0,
I2C_SMBUS_I2C_BLOCK_DATA, );
and the logs show me that this hits the else part of this if condition in
i801_block_transaction function
BTW. I need to know urgently what HW is broken by this
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Thu, 2007-12-20 at 21:11 -0800, Greg KH wrote:
> On Fri, Dec 21, 2007 at 03:47:28PM +1100, Benjamin Herrenschmidt wrote:
> > pci: Remove pci_enable_device_bars() fix for qla
> >
> > The previous patch missed one occurence of pci_enable_device_bars()
> > in the qla2xxx driver. This fixes it.
>
On Thu, Dec 20, 2007 at 09:53:54PM +, Adrian McMenamin wrote:
> On 16/12/2007, Paul Mundt <[EMAIL PROTECTED]> wrote:
> > Also, __devinit/__devexit annotations?
> >
>
> Is there any difference between __init and __devint?
Yes.
--
To unsubscribe from this list: send the line "unsubscribe
Jeff Moyer pointed out that a mount; umount loop of ecryptfs,
with the same cipher & other mount options, created a new
ecryptfs_key_tfm_cache item each time, and the cache could
grow quite large this way.
Looking at this with mhalcrow, we saw that ecryptfs_parse_options()
unconditionally called
hello,
I have some questions for your patches.
> Paravirt and alternatives are always done when SMP is
> inactive, so there is no
> need to use locks.
> -#ifndef CONFIG_KPROBES
> -#ifdef CONFIG_HOTPLUG_CPU
> - /* It must still be possible to apply SMP alternatives. */
> - if
On Fri, Dec 21, 2007 at 03:47:28PM +1100, Benjamin Herrenschmidt wrote:
> pci: Remove pci_enable_device_bars() fix for qla
>
> The previous patch missed one occurence of pci_enable_device_bars()
> in the qla2xxx driver. This fixes it.
Should I just merge this with your 2/3 patch so everything is
On Thu, 20 Dec 2007, Linus Torvalds wrote:
>
> And here's the git patch to avoid this optimization when there is
> context.
Actually, the code to finding one '\n' is still needed to avoid the
(pathological) case of getting a "\No newline", so scrap that one which
was too aggressive, and use
> I do have TCP Sequence # Randomization enabled on my router.
Huh? Do you mean a PIX blade in a Cisco switch-router chassis? It
would be very useful if you could be less vague about the
equipment in use.
> However,
> if this was causing an issue, wouldn't it always occur and cause
>
On Thu, Dec 20, 2007 at 08:40:54PM -0800, Linus Torvalds wrote:
> That was a rather long-winded explanation of what happened, mainly because
> it was all very unexpected to me, and I had personally mistakenly thought
> the git optimization was perfectly valid and actually had to go through
>
Benjamin Herrenschmidt wrote:
Sounds good. Thanks!
Note, that these smaller sub-host-page-sized mappings might pollute the
address space causing full aligned host-page-size maps to become
scarce... Maybe there's a clever way to keep those in their own segment
of the address space?
We
pci: Remove pci_enable_device_bars() fix for qla
The previous patch missed one occurence of pci_enable_device_bars()
in the qla2xxx driver. This fixes it.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
---
Index: linux-merge/drivers/scsi/qla2xxx/qla_def.h
> > It was just
> >
> > while echo ; do cat /sys/kernel/ ; done
> >
> > it's all in the email threads somewhere..
>
> The patch that was posted in the thread that I mentioned earlier is here.
> I ran the test for 15 minutes and things are still fine.
>
>
>
> quicklist: Set
On Thu, 2007-12-20 at 20:28 -0800, Greg KH wrote:
> On Thu, Dec 20, 2007 at 03:28:10PM +1100, Benjamin Herrenschmidt wrote:
> > Now that all in-tree users are gone, this removes pci_enable_device_bars()
> > completely.
>
> Hm, looks like you missed drivers/scsi/qla2xxx/qla_os.c
>
> Quick,
On Thu, 20 Dec 2007, Linus Torvalds wrote:
>
> It only happened for a few files that had lots of repeated lines - so that
> the diff could literally be done multiple different ways - and in fact,
> the file that caused the problems really had a bogus commit that
> duplicated *way* too much
On Fri, 21 Dec 2007 14:26:47 +1100
Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Friday 21 December 2007 13:28:34 FUJITA Tomonori wrote:
> > I'm not sure about chaining the headers (as your sg_ring and
> > scsi_sgtable do) would simplify LLDs. Have you looked at ips or
> > qla1280?
>
> Not yet,
On Thu, Dec 20, 2007 at 03:28:10PM +1100, Benjamin Herrenschmidt wrote:
> Now that all in-tree users are gone, this removes pci_enable_device_bars()
> completely.
Hm, looks like you missed drivers/scsi/qla2xxx/qla_os.c
Quick, before akpm gets mad at you for breaking the build, send me a
patch!
On Thu, 20 Dec 2007, Linus Torvalds wrote:
>
> The tar-ball and the git archive itself is fine, but yes, the diff from
> 2.6.23 to 2.6.24-rc6 is bad. It's the "trim_common_tail()" optimization
> that has caused way too much pain.
Very interesting breakage. The patch was actually "correct" in
Loic Prylli wrote:
Just curious, do you know of any system where that recommendation was
not followed? On all motherboards where I have seen a AMD-8131 or a
AMD-8132, they were alone on their hypertransport link, and other
"northbridges" (more precisely hypertransport to pci-express or
On Thu, 20 Dec 2007, Kyle McMartin wrote:
>
> I think I see the problem, it's lack of context in the diff,
No, the problem is that "git diff" is apparently broken by a recent
optimization. The diff is simply broken.
The tar-ball and the git archive itself is fine, but yes, the diff from
On Thu, Dec 20, 2007 at 07:49:05PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 20 Dec 2007, Kyle McMartin wrote:
> >
> > I think I see the problem, it's lack of context in the diff,
>
> No, the problem is that "git diff" is apparently broken by a recent
> optimization. The diff is simply
On 12/20/2007 9:15 PM, Robert Hancock wrote:
>>
>> Suggested Workaround
>>
>> It is strongly recommended that system designers do not connect the
>> AMD-8132 and devices that use extended
>> configuration space MMIO BARs (ex: HyperTransport-to-PCI Express®
>> bridges) to the same processor
>>
Mathieu Desnoyers wrote:
Argh.. Rusty asked to have a simplified version first, and then to
implement the "more complex" one on top of it. However, in order to get
the reentrancy I need for the markers, I need the complex version of the
immediate values. Therefore, you find, in this patchset,
On Friday 21 December 2007 13:28:34 FUJITA Tomonori wrote:
> I'm not sure about chaining the headers (as your sg_ring and
> scsi_sgtable do) would simplify LLDs. Have you looked at ips or
> qla1280?
Not yet, am working my way through the drivers, but I don't expect it will be
a simplification to
Otherwise patch gets horribly confused and falls over applying
the diff. Not sure why these were being defined twice.
Signed-off-by: Kyle McMartin <[EMAIL PROTECTED]>
---
Well, we can get it fixed for -git1, I respun the patch-2.6.24-rc6 diff
with git diff -p v2.6.23..HEAD and applied it to a
* H. Peter Anvin ([EMAIL PROTECTED]) wrote:
> This patch is modified by another patch in the sequence. This feels
> needlessly confusing when reviewing (especially since the comment doesn't
> look to match the code, e.g. w.r.t to "Q" and "R" constraints); can you
> reorder the patchset to
From: Matt Mackall <[EMAIL PROTECTED]>
Date: Thu, 20 Dec 2007 19:06:55 -0600
> @@ -707,7 +707,10 @@ static ssize_t kpagecount_read(struct fi
> return -EIO;
>
> while (count > 0) {
> - ppage = pfn_to_page(pfn++);
> + ppage = 0;
> + if
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Thu, 20 Dec 2007 18:15:32 -0800
> No-period is a kernel idiom, produces perfectly readable output, I have
> never ever heard of anyone expressing the least concern over a lack of dots
> at the end of their printks and 91% of kernel code agrees.
I
On Sat, Dec 01, 2007 at 02:06:58AM -0700, Eric W. Biederman wrote:
>
> Now that we have network namespace support merged it is time to
> revisit the sysfs support so we can remove the dependency on !SYSFS.
Oops, I forgot to apply this to my tree. Eric, you still want this
submitted, right?
This patch is modified by another patch in the sequence. This feels
needlessly confusing when reviewing (especially since the comment
doesn't look to match the code, e.g. w.r.t to "Q" and "R" constraints);
can you reorder the patchset to avoid that?
-hpa
--
To unsubscribe from this
This is a note to let you know that I've just added the patch titled
Subject: PCI: Remove users of pci_enable_device_bars()
to my gregkh-2.6 tree. Its filename is
pci-remove-users-of-pci_enable_device_bars.patch
This tree can be found at
On Thu, Dec 20, 2007 at 09:48:05PM -0500, Kyle McMartin wrote:
> 1 out of 3 hunks FAILED -- saving rejects to file
> drivers/video/mbx/reg_bits.h.rej
> error: Bad exit status from /var/tmp/rpm-tmp.22316 (%prep)
>
I think I see the problem, it's lack of context in the diff,
commit
This is a note to let you know that I've just added the patch titled
Subject: PCI: Remove pci_enable_device_bars()
to my gregkh-2.6 tree. Its filename is
pci-remove-pci_enable_device_bars.patch
This tree can be found at
This is a note to let you know that I've just added the patch titled
Subject: PCI: Add pci_enable_device_{io,mem} intefaces
to my gregkh-2.6 tree. Its filename is
pci-add-pci_enable_device_-io-mem-intefaces.patch
This tree can be found at
This is a note to let you know that I've just added the patch titled
Subject: PCI: correctly initialize a structure for pcie_save_pcix_state()
to my gregkh-2.6 tree. Its filename is
pci-correctly-initialize-a-structure-for-pcie_save_pcix_state.patch
This tree can be found at
On Friday 21 December 2007 11:40:00 David Miller wrote:
> From: Rusty Russell <[EMAIL PROTECTED]>
> Date: Fri, 21 Dec 2007 11:35:12 +1100
>
> > On Friday 21 December 2007 11:00:27 FUJITA Tomonori wrote:
> > > We need to pass the whole sg entries to the IOMMUs at a time.
> >
> > Hi Fujita,
> >
> >
On Thu, Dec 20, 2007 at 05:41:09PM -0800, Linus Torvalds wrote:
> The regression list keeps shrinking, so we're still on track for a full
> 2.6.24 release in early January. Assuming we don't all overeat during the
> holidays and nobody gets any work done. But we all know that the holidays
> are
Robert Hancock wrote:
I have to wonder why certain system
designers then didn't follow their strong recommendation..
I don't think I want to go there.
I used to be a hardware/firmware guy.
:D :D
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Thu, 2007-12-20 at 17:41 -0800, Linus Torvalds wrote:
> The most noticeable part here (both to users and in the diffstat) should
> be the libata-acpi fixes by Tejun Heo, which should hopefully take care of
> all of the regressions that were caused by teaching SATA about doing the
> proper
On Wed, 12 Dec 2007 15:38:26 -0800 Harvey Harrison <[EMAIL PROTECTED]> wrote:
> Andrew, I'm not sure who is best to hit with these final dribs and
> drabs removing fastcall. Once all of these have hit Linus' tree
> I will send a final patch deleting the include/linux/linkage.h
> definitions as
On Thu, Dec 20, 2007 at 04:14:05PM -0700, Eric W. Biederman wrote:
> Remains the question whether it is intended that many, perhaps even
> large, tables are compiled in without ever having a chance to get used,
> i.e. whether there shouldn't #ifdef CONFIG_xxx get added.
> -static struct
The sense buffer ins scsi_cmnd can nowadays be DMA'ed into directly
by some low level drivers (that typically happens with USB mass
storage).
This is a problem on non cache coherent architectures such as
embedded PowerPCs where the sense buffer can share cache lines with
other structure members,
This patch based on some earlier work by Roland Dreier introduces
a pair of annotations that can be used to enforce alignment of
objects that can be DMA'ed into, and to enforce that an DMA'able
object within a structure isn't sharing a cache line with some
other object.
Such sharing of a data
On Fri, 21 Dec 2007 10:13:38 +1100
Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Thursday 20 December 2007 18:58:07 David Miller wrote:
> > From: Rusty Russell <[EMAIL PROTECTED]>
> > Date: Thu, 20 Dec 2007 18:53:48 +1100
> >
> > > Manipulating the magic chains is horrible; it looks simple to the
> So in your case, it should *result* in the exact same situation that your
> patch did, but at the same time, when dealing with the (more common) case
> of smaller allocations, we still continue to try to avoid being too close
> to the top-of-memory.
>
> So it's not perfect, but perhaps it
On Thu, 20 Dec 2007 16:40:00 -0800 (PST)
David Miller <[EMAIL PROTECTED]> wrote:
> From: Rusty Russell <[EMAIL PROTECTED]>
> Date: Fri, 21 Dec 2007 11:35:12 +1100
>
> > On Friday 21 December 2007 11:00:27 FUJITA Tomonori wrote:
> > > We need to pass the whole sg entries to the IOMMUs at a time.
Tony Camuso wrote:
Robert Hancock wrote:
First off, I would like to see confirmation from the horses's mouths
here (namely AMD, ServerWorks/Broadcom, and whoever else) that there
is no other way to get around this problem than disabling MMCONFIG for
accesses behind those chips.
I happen
On Fri, 21 Dec 2007 02:43:33 +0100 Frans Pop <[EMAIL PROTECTED]> wrote:
> On Thursday 20 December 2007, Alan Cox wrote:
> > The kernel printk messages are sentences.
>
> I'm afraid that I completely and utterly disagree. Kernel messages are _not_
> sentences. The vast majority is not
Robert Hancock wrote:
The case of the device built into the K8 northbridge that's unreachable
by MMCONFIG kind of makes sense, since the northbridge is what's
translating the MMCONFIG memory access into config accesses. It seems
bizarre to me that a bridge chip could possibly have such a
On 12/20/2007 6:21 PM, Tony Camuso wrote:
>
> And the MMCONFIG problem with enterprise systems and workstations, where
> we do control the BIOS (for the most part), is due to known bugs in
> certain versions of certain chipsets, HT1000, AMD8132, among them, not
> the BIOS.
The lack of MMCONFIG
Ok, so after the holidays I will do the following:
let memtest86+ run several hours.
do a full backup to switch to r3 and build an unpatched kernel.
see if I can reproduce the oops with .21 and .22 (because AFAIR no oops with
21.. but I might be wrong).
Not exactly in that order.
Glück Auf
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]
CC: Thomas Gleixner <[EMAIL
On Friday 21 December 2007 06:24, Linus Torvalds wrote:
> On Thu, 20 Dec 2007, Jan Kara wrote:
> > As I wrote in my previous email, this solution works but hides the
> > fact that the page really *has* dirty data in it and *is* pinned in
> > memory until the commit code gets to writing it. So in
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
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]
CC: Thomas Gleixner <[EMAIL PROTECTED]>
CC: Ingo Molnar <[EMAIL PROTECTED]>
CC: H. Peter Anvin <[EMAIL
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
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 _imv_read()
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.
Changelog:
Move the kernel_text_lock/unlock out of the for loops.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
Acked-by: Ananth N
PowerPC optimization of the immediate values which uses a li instruction,
patched with an immediate value.
Changelog:
- Put imv_set and _imv_set in the architecture independent header.
- Pack the __imv section. Use smallest types required for size (char).
- Remove architecture specific update
Changelog:
- Remove imv_set_early (removed from API).
- Use imv_* instead of immediate_*.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Rusty Russell <[EMAIL PROTECTED]>
---
Documentation/immediate.txt | 221
1 file changed, 221
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
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]
---
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.
Add text_poke_early, for alternatives and paravirt boot-time and module load
time patching.
Hi Andrew,
Here are the patches that would be interesting to queue for 2.6.25. As you
asked, the patchset applies to 2.6.24-rc5-mm1.
It includes those logical changes and applies in the following order.
Thanks,
Mathieu
#Text Edit Lock
kprobes-use-mutex-for-insn-pages.patch
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]
CC: Thomas Gleixner <[EMAIL
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.
It uses a breakpoint to bypass the instruction being changed, which lessens the
interrupt latency of the operation and protects against NMIs
Add a __discard sectionto the linker script. Code produced in this section will
not be put in the vmlinux file. This is useful when we have to calculate the
size of an instruction before actually declaring it (for alignment purposes for
instance). This is used by the immediate values.
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"
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]
CC: Thomas Gleixner <[EMAIL PROTECTED]>
CC: Ingo Molnar <[EMAIL PROTECTED]>
CC: H. Peter Anvin <[EMAIL
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 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
Use an atomic update for immediate values.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
CC: Rusty Russell <[EMAIL PROTECTED]>
CC: Christoph Hellwig <[EMAIL PROTECTED]>
CC: Paul Mackerras <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/Makefile|1
arch/powerpc/kernel/immediate.c |
- Needed on architectures where we must surround live instruction modification
with "WP flag disable".
- Turns into a memcpy on powerpc since there is no WP flag activated for
instruction pages (yet..).
- Add empty sync_core to powerpc so it can be used in architecture independent
code.
Use immediate values with lower d-cache hit in optimized version as a
condition for scheduler profiling call.
Changelog :
- Use imv_* instead of immediate_*.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |3 ++-
include/linux/profile.h |5 +++--
Make markers use immediate values.
Changelog :
- Use imv_* instead of immediate_*.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
Documentation/markers.txt | 17 +
include/linux/marker.h| 42 --
kernel/marker.c
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]>
---
Remove the architecture agnostic code now replaced by architecture specific,
atomic instruction updates.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
---
include/linux/immediate.h | 11
kernel/immediate.c| 113 +-
2 files
Pavel Emelyanov wrote:
> Oren Laadan wrote:
>> Serge E. Hallyn wrote:
>>> Quoting Pavel Emelyanov ([EMAIL PROTECTED]):
Oren Laadan wrote:
> Serge E. Hallyn wrote:
>> Quoting Oren Laadan ([EMAIL PROTECTED]):
>>> I hate to bring this again, but what if the admin in the container
On Thursday 20 December 2007, Alan Cox wrote:
> The kernel printk messages are sentences.
I'm afraid that I completely and utterly disagree. Kernel messages are _not_
sentences. The vast majority is not well-formed and does not contain any of
the elements that are required for a proper
Robert Hancock wrote:
First off, I would like to see confirmation from the horses's mouths
here (namely AMD, ServerWorks/Broadcom, and whoever else) that there
is no other way to get around this problem than disabling MMCONFIG for
accesses behind those chips.
And here are the excerpts
1 - 100 of 1372 matches
Mail list logo
