From: Keir Fraser <keir.xen@gmail.com>
To: Xinxin Jin <xinxinjin89@gmail.com>, Xen-devel@lists.xen.org
Subject: Re: What is fastcall in Xen?
Date: Thu, 25 Oct 2012 16:38:18 -0700 [thread overview]
Message-ID: <CCAF1B7A.428CB%keir.xen@gmail.com> (raw)
In-Reply-To: <CAJJWZczzOPxcBOkAvnohA5Fw_-k_WfjfVvGyFNRYBUAiUOMnVg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 359 bytes --]
No, fastcall is defined away to nothing.
On 25/10/2012 16:11, "Xinxin Jin" <xinxinjin89@gmail.com> wrote:
> Hi, I found some interrupt handler functions are declared with "fastcall"
> keyword, such as:
> fastcall void event_check_interrupt(void);
> So what does fastcall implicate here? Is there some special things in the
> fastcall handling ?
> Thanks,
[-- Attachment #1.2: Type: text/html, Size: 772 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:[~2012-10-25 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:11 What is fastcall in Xen? Xinxin Jin
2012-10-25 23:38 ` Keir Fraser [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=CCAF1B7A.428CB%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Xen-devel@lists.xen.org \
--cc=xinxinjin89@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).