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: Tue, 4 Oct 2005 18:45:20 +0200 [thread overview]
Message-ID: <200510041845.20902.ak@suse.de> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173056C8BBF@scsmsx402.amr.corp.intel.com>
On Tuesday 04 October 2005 18:03, Nakajima, Jun wrote:
>
> I don't think we should use "int N" sacrificing the good feature for
> 64-bit when we can handle 32-bit hypercalls using a compatibility layer.
> I also think using the existing ABI convention is much better whenever
> possible and appropriate because we don't need to re-invent the wheel.
> After all, the only difference between system call and hyper call
> basically is the system/hypercall number.
Main 32bit linux solves this problem by mapping a vsyscall page into the
address space. The ABI is then just to jump to an appropiate entry point in
it. The entry point uses the right instruction then.
-Andi
next prev parent reply other threads:[~2005-10-04 16:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 16:03 32/64-bit hypercall interface Nakajima, Jun
2005-10-04 16:45 ` Andi Kleen [this message]
-- 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-03 22:03 Ian Pratt
2005-10-04 18:05 ` Hollis Blanchard
2005-10-05 10:22 ` Keir Fraser
2005-10-03 21:24 Nakajima, Jun
2005-10-04 12:11 ` Andi Kleen
2005-10-04 16:15 ` Hollis Blanchard
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=200510041845.20902.ak@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.