From: Andi Kleen <ak@suse.de>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Jeremy Katz <katzj@redhat.com>,
xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Subject: Re: 32/64-bit hypercall interface
Date: 04 Oct 2005 14:11:10 +0200 [thread overview]
Message-ID: <p73br251nz5.fsf@verdi.suse.de> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173056C83B9@scsmsx402.amr.corp.intel.com>
"Nakajima, Jun" <jun.nakajima@intel.com> writes:
>
> The 32-bit and 64-bit hypercall ABI cannot be identical on x86 because
> of the generic ABI difference between 32-bit and 64-bit.
You use a custom ABI for hypercalls anyways, so you can define
it to be the same with some care. That is the approach that is
used by some newer subsystems in the Linux kernel.
In my experience even people with the best intentions tend to get that
wrong at some point because there are some subtle issues so having the
additional safety net of a compat layer is still a good idea. It would
only emulate the ones that went wrong.
-Andi
next prev parent reply other threads:[~2005-10-04 12:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 21:24 32/64-bit hypercall interface Nakajima, Jun
2005-10-04 12:11 ` Andi Kleen [this message]
2005-10-04 16:15 ` Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 21:51 Nakajima, Jun
2005-10-04 22:47 ` Hollis Blanchard
2005-10-04 16:03 Nakajima, Jun
2005-10-04 16:45 ` Andi Kleen
2005-10-03 22:03 Ian Pratt
2005-10-04 18:05 ` Hollis Blanchard
2005-10-05 10:22 ` Keir Fraser
2005-10-03 19:56 Ian Pratt
2005-10-03 20:04 ` Jeremy Katz
2005-10-03 21:11 ` Hollis Blanchard
2005-10-03 22:00 ` Keir Fraser
2005-10-04 16:27 ` Hollis Blanchard
2005-10-04 12:08 ` Andi Kleen
2005-10-03 19:11 Nakajima, Jun
2005-10-03 19:28 ` Hollis Blanchard
2005-10-02 21:21 Ian Pratt
2005-10-01 18:25 Nakajima, Jun
2005-10-03 16:11 ` Jeremy Katz
2005-09-29 13:56 Ian Pratt
2005-09-29 18:17 ` Hollis Blanchard
2005-09-29 20:12 ` Hollis Blanchard
2005-09-29 22:26 ` Keir Fraser
2005-09-29 22:43 ` Keir Fraser
2005-09-30 0:54 ` Andrei Petrov
2005-09-30 8:03 ` Keir Fraser
2005-09-30 15:38 ` Jimi Xenidis
2005-09-30 20:05 ` Ronald G Minnich
2005-09-30 20:28 ` Hollis Blanchard
2005-09-30 20:39 ` Ronald G Minnich
2005-09-30 15:39 ` Hollis Blanchard
2005-09-30 15:45 ` Keir Fraser
2005-09-30 16:34 ` Hollis Blanchard
2005-09-30 16:42 ` Keir Fraser
2005-09-30 17:03 ` Hollis Blanchard
2005-10-01 1:33 ` Jeremy Katz
2005-10-03 19:34 ` Kip Macy
2005-09-30 16:44 ` David
2005-09-30 16:44 ` Keir Fraser
2005-09-30 16:57 ` Hollis Blanchard
2005-09-30 16:55 ` Andrei Petrov
2005-10-03 18:18 ` Hollis Blanchard
2005-09-28 21:36 Hollis Blanchard
2005-09-29 9:00 ` Keir Fraser
2005-09-29 12:41 ` Jimi Xenidis
2005-09-29 13:13 ` Keir Fraser
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=p73br251nz5.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=jun.nakajima@intel.com \
--cc=katzj@redhat.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.