mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Andi Kleen <ak@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: [2.6.23-rc1 REGRESSION] CPU hotplug totally broken on HPC nx6325 (x86_64)
Date: Mon, 30 Jul 2007 19:16:22 -0700	[thread overview]
Message-ID: <20070731021622.GE3673@sequoia.sous-sol.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707301845380.4161@woody.linux-foundation.org>

* Linus Torvalds (torvalds@linux-foundation.org) wrote:
> On Mon, 30 Jul 2007, Chris Wright wrote:
> > This also fixes paravirt patching which was broken when text_poke()
> > tried to patch the various pv ops in lookup_address.
> 
> Hmm. What is "this"? The revert? 

Yes, sorry, your revert also fixes paravirt patching.

> That said, I do wonder whether virtualization still has problems with 
> CONFIG_RODATA, though. We limit the RODATA memory ranges based on KPROBES 
> and HOTPLUG_CPU, but not based on VIRTUALIZATION.
> 
> I'd expect any virtualization fixups to hit the same problems that the SMP 
> alternatives hit. No?

Hmm, patching should've already happened, and aside of module loading,
isn't typically done again.  I think it's OK as it is.

thanks,
-chris

      reply	other threads:[~2007-07-31  2:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 12:40 Rafael J. Wysocki
2007-07-26 16:43 ` Linus Torvalds
2007-07-26 19:22   ` Rafael J. Wysocki
2007-07-26 19:59     ` Linus Torvalds
2007-07-31  1:23   ` Chris Wright
2007-07-31  1:50     ` Linus Torvalds
2007-07-31  2:16       ` Chris Wright [this message]

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=20070731021622.GE3673@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®