From: "Jan Beulich" <jbeulich@novell.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Andi Kleen" <ak@suse.de>, <linux-kernel@vger.kernel.org>,
<patches@x86-64.org>
Subject: Re: [PATCH] x86: make SMP locks handling interact properly with CONFIG_DEBUG_RODATA (2nd try)
Date: Wed, 04 Jul 2007 17:29:54 +0100 [thread overview]
Message-ID: <468BE722.76E4.0078.0@novell.com> (raw)
In-Reply-To: <468BBFB3.9080303@goop.org>
>>> Jeremy Fitzhardinge <jeremy@goop.org> 04.07.07 17:41 >>>
>Jan Beulich wrote:
>> Instead of suppressing the change of .text to become readonly, make
>> the SMP locks patching code properly adjust/restore the page access
>> rights.
>>
>
>I guess we'll need to do the same thing for paravirt_ops patching?
No, the patch already does this (as long as there no code to do that other
than in alternatives.c).
>> On x86-64 additionally remove all mappings past the kernel image, and
>> remove leftovers from the removal of the more general (but abandoned)
>> SMP alternatives.
>>
>
>I'd already posted a patch to remove smp alternatives. I thought it had
>been merged already, but I guess it's in Andi's queue.
Oh, sorry, I forgot to remove that part of the comment after merging up to
2.6..22-rcX.
Jan
next prev parent reply other threads:[~2007-07-04 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 6:33 [PATCH] x86: make SMP locks handling interact properly with CONFIG_DEBUG_RODATA (2nd try) Jan Beulich
2007-07-04 15:41 ` Jeremy Fitzhardinge
2007-07-04 16:15 ` Andi Kleen
2007-07-04 16:44 ` Jeremy Fitzhardinge
2007-07-04 16:29 ` Jan Beulich [this message]
2007-07-04 17:51 ` Dave Jones
2007-07-04 18:09 ` Jeremy Fitzhardinge
2007-07-17 17:54 ` Andi Kleen
2007-07-17 20:55 ` Mathieu Desnoyers
2007-07-18 6:00 ` Jan Beulich
2007-07-17 17:57 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2007-07-04 16:31 Jan Beulich
2007-07-04 16:46 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=468BE722.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox