From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Carl Patenaude Poulin <carl.patenaudepoulin@mail.mcgill.ca>,
xen-devel@lists.xen.org
Subject: Re: Xen hypercall calling convention
Date: Fri, 4 Dec 2015 10:08:25 +0000 [thread overview]
Message-ID: <56616619.7080300@citrix.com> (raw)
In-Reply-To: <CA+v+NpKnVAHiTNvJDuby8iLAVHm6Jpe-5MskO1P5BrBixtaq+g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1012 bytes --]
On 04/12/15 03:21, Carl Patenaude Poulin wrote:
> Hi folks,
>
> On page 12 of "The Definitive Guide to the Xen Hypervisor", it is
> mentioned that "Xen, like Linux, uses the MS-DOS calling convention,
> rather than the UNIX convention used by FreeBSD."
>
> I keep digging online and I can't find any information about an
> "MS-DOS calling convention".
Second google link,
www.agner.org/optimize/calling_conventions.pdf
except that you want to be looking for Windows 16bit as its alternative
name.
> We've already reverse engineered which registers are used in what
> order from the Mini-OS source code, but I'm wondering if there's a
> specification of this calling convention floating anywhere.
The in-tree public header files are the authoritative source of
information, so
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/arch-x86/xen-x86_32.h;hb=HEAD
and
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/arch-x86/xen-x86_64.h;hb=HEAD
respectively.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2650 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-12-04 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 3:21 Xen hypercall calling convention Carl Patenaude Poulin
2015-12-04 10:08 ` Andrew Cooper [this message]
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=56616619.7080300@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=carl.patenaudepoulin@mail.mcgill.ca \
--cc=xen-devel@lists.xen.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 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.