From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>, Ingo Molnar <mingo@elte.hu>,
Petr Vandrovec <petr@vmware.com>,
Pratap Subrahmanyam <pratap@vmware.com>,
Dan Hecht <dhecht@vmware.com>, Dan Arai <arai@vmware.com>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Chaz Masden <zamsden@gmail.com>, Zachary Amsden <zach@vmware.com>
Subject: [RFC, PATCH 0/5] Paravirt: fix export of paravirt-ops to binary modules
Date: Thu, 19 Apr 2007 18:52:14 -0700 (PDT) [thread overview]
Message-ID: <20070420015214.6834BBFC@zach-dev2.vmware.com> (raw)
A clever set of manipulations allows us to fix binary modules with paravirt-ops
by just not exporting paravirt_ops at all and using the new patching code.
What do you think? Experimental patches here... only partially tested, but
booting and appear to be a working prototype.
Thanks,
Zach
next reply other threads:[~2007-04-20 1:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 1:52 Zachary Amsden [this message]
2007-04-20 9:34 ` [RFC, PATCH 0/5] Paravirt: fix export of paravirt-ops to binary modules Andi Kleen
2007-04-20 15:03 ` Jeremy Fitzhardinge
2007-04-20 21:25 ` Zachary Amsden
2007-04-20 21:33 ` Jeremy Fitzhardinge
2007-04-20 21:36 ` Zachary Amsden
2007-04-20 23:01 ` Jeremy Fitzhardinge
2007-04-20 23:02 ` Zachary Amsden
2007-04-22 23:37 ` Rusty Russell
2007-04-22 23:49 ` Andi Kleen
2007-04-23 0:24 ` Rusty Russell
2007-04-23 0:49 ` Andi Kleen
2007-04-23 1:04 ` Rusty Russell
2007-04-23 21:18 ` Zachary Amsden
2007-04-23 1:00 ` 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=20070420015214.6834BBFC@zach-dev2.vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arai@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=dhecht@vmware.com \
--cc=jeremy@goop.org \
--cc=mingo@elte.hu \
--cc=petr@vmware.com \
--cc=pratap@vmware.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=zamsden@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).