From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@suse.de>, Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7
Date: Mon, 09 Jul 2007 07:06:34 -0700 [thread overview]
Message-ID: <469240EA.8000301@goop.org> (raw)
In-Reply-To: <20070709103223.5bfe24d4@the-village.bc.nu>
Alan Cox wrote:
> There were a considerable number of sensible logical objections. You just
> didn't agree with them. You've now effectively made .22 unsupportable
> since we don't know if someone has binary virtualiser crap loaded.
The pv_ops infrastructure doesn't support modular pv_ops
implementations, and if it did, there's certainly no intention of
supporting non-GPL implementations.
At the same time that all the other altinstruction patching happens, it
converts any indirect calls via paravirt_ops into direct calls to the
target function, bypassing struct paravirt_ops altogether. After that
the structure is pretty much only used for patching modules. Any
attempt at writing a modular pv_ops implementation would fail as a result.
J
next prev parent reply other threads:[~2007-07-09 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 21:42 Please revert 21564fd2a3deb48200b595332f9ed4c9f311f2a7 Adrian Bunk
2007-06-18 4:43 ` Jeremy Fitzhardinge
2007-07-08 22:44 ` Adrian Bunk
2007-07-08 23:02 ` Andi Kleen
2007-07-08 23:17 ` Adrian Bunk
2007-07-09 9:39 ` Andi Kleen
2007-07-09 10:06 ` Alan Cox
2007-07-09 10:35 ` Andi Kleen
2007-07-09 9:32 ` Alan Cox
2007-07-09 9:39 ` Andi Kleen
2007-07-09 14:06 ` Jeremy Fitzhardinge [this message]
2007-07-09 2:46 ` Jeremy Fitzhardinge
2007-07-09 9:51 ` Alan Cox
2007-07-09 13:55 ` 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=469240EA.8000301@goop.org \
--to=jeremy@goop.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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