From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alexander Graf <agraf@suse.de>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
Amit Shah <amit.shah@redhat.com>,
Elsie Wahlig <elsie.wahlig@amd.com>,
"Serebrin,
Benjamin (Calendar)" <Benjamin.Serebrin@exchange.amd.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: Cross vendor migration ideas
Date: Thu, 13 Nov 2008 12:20:58 +0200 [thread overview]
Message-ID: <491BFF8A.8010800@redhat.com> (raw)
In-Reply-To: <491AFA36.4040909@codemonkey.ws>
Anthony Liguori wrote:
>
> I wonder if patching is an option?
You would need to patch the syscall/sysenter and sysret/sysexit sites,
as well as the kernel entry points, since the calling conventions are
dissimilar. Finding a place to put the stubs would be difficult, at best.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-13 10:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 15:39 Cross vendor migration ideas Alexander Graf
2008-11-12 15:45 ` Anthony Liguori
2008-11-12 15:50 ` Alexander Graf
2008-11-12 15:59 ` Anthony Liguori
2008-11-13 0:02 ` Skywing
2008-11-13 1:48 ` Serebrin, Benjamin (Calendar)
2008-11-15 13:03 ` Andi Kleen
2008-11-15 16:39 ` Alexander Graf
2008-11-15 17:37 ` Andi Kleen
2008-11-16 15:36 ` Avi Kivity
2008-11-17 11:09 ` Andi Kleen
2008-11-17 11:59 ` Avi Kivity
2008-11-15 17:38 ` Glauber Costa
2008-11-16 14:58 ` Avi Kivity
2008-11-13 10:16 ` Avi Kivity
2008-11-12 20:06 ` Andi Kleen
2008-11-12 20:52 ` Alexander Graf
2008-11-13 10:20 ` Avi Kivity [this message]
2008-11-12 16:52 ` Amit Shah
2008-11-12 17:19 ` Alexander Graf
2008-11-13 4:35 ` Amit Shah
2008-11-13 13:38 ` Alexander Graf
2008-11-14 13:07 ` Amit Shah
2008-11-14 23:43 ` Nitin A Kamble
2008-11-17 10:07 ` Amit Shah
-- strict thread matches above, loose matches on Subject: below --
2008-11-16 0:23 Skywing
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=491BFF8A.8010800@redhat.com \
--to=avi@redhat.com \
--cc=Benjamin.Serebrin@exchange.amd.com \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=elsie.wahlig@amd.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.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