public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Jan Beulich <jbeulich@novell.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	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, 4 Jul 2007 18:15:58 +0200	[thread overview]
Message-ID: <200707041815.58923.ak@suse.de> (raw)
In-Reply-To: <468BBFB3.9080303@goop.org>

On Wednesday 04 July 2007 17:41:39 Jeremy Fitzhardinge wrote:
> 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?

Not if the patching happens early enough at boot. That's true for Xen
and lguest, but I'm not sure about VMI

-Andi


  reply	other threads:[~2007-07-04 16:16 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 [this message]
2007-07-04 16:44     ` Jeremy Fitzhardinge
2007-07-04 16:29   ` Jan Beulich
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=200707041815.58923.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jbeulich@novell.com \
    --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