From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH 2/2] docs: Introduce some hypercall page documentation
Date: Thu, 23 May 2019 12:01:51 +0100 [thread overview]
Message-ID: <701d553c-20a8-7b1a-6023-35ed1008ce65@citrix.com> (raw)
In-Reply-To: <5CE67C5B0200007800231A83@prv1-mh.provo.novell.com>
On 23/05/2019 11:56, Jan Beulich wrote:
>>>> On 23.05.19 at 12:20, <andrew.cooper3@citrix.com> wrote:
>> This also introduced the top-level Guest Documentation section.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Large parts of this are entirely x86-centric, yet hypercalls exist
> for Arm as well. If this is intentional, then I think you should say
> so above.
It is all x86 specific, which is why it is grouped under "x86 guest
documentation".
As for future plans, the actual hypercalls will live in the architecture
neutral guest documentation section.
ARM doesn't actually use anything here, because they have a single
spec-defined instruction for making hypercalls which exists in all
virt-capable hardware.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [Xen-devel] [PATCH 2/2] docs: Introduce some hypercall page documentation
Date: Thu, 23 May 2019 12:01:51 +0100 [thread overview]
Message-ID: <701d553c-20a8-7b1a-6023-35ed1008ce65@citrix.com> (raw)
Message-ID: <20190523110151.Y394BR6Rgo8Wqn0gl26VoPtFFemUpK20qo9JtohLBrs@z> (raw)
In-Reply-To: <5CE67C5B0200007800231A83@prv1-mh.provo.novell.com>
On 23/05/2019 11:56, Jan Beulich wrote:
>>>> On 23.05.19 at 12:20, <andrew.cooper3@citrix.com> wrote:
>> This also introduced the top-level Guest Documentation section.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Large parts of this are entirely x86-centric, yet hypercalls exist
> for Arm as well. If this is intentional, then I think you should say
> so above.
It is all x86 specific, which is why it is grouped under "x86 guest
documentation".
As for future plans, the actual hypercalls will live in the architecture
neutral guest documentation section.
ARM doesn't actually use anything here, because they have a single
spec-defined instruction for making hypercalls which exists in all
virt-capable hardware.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-23 11:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 10:20 [PATCH 0/2] Hypercall page docs and code cleanup Andrew Cooper
2019-05-23 10:20 ` [Xen-devel] " Andrew Cooper
2019-05-23 10:20 ` [PATCH 1/2] x86: init_hypercall_page() cleanup Andrew Cooper
2019-05-23 10:20 ` [Xen-devel] " Andrew Cooper
2019-05-23 10:23 ` Wei Liu
2019-05-23 10:23 ` [Xen-devel] " Wei Liu
2019-05-23 10:49 ` Jan Beulich
2019-05-23 10:49 ` [Xen-devel] " Jan Beulich
2019-05-28 5:31 ` Tian, Kevin
2019-05-28 5:31 ` [Xen-devel] " Tian, Kevin
2019-06-19 16:17 ` Woods, Brian
2019-05-23 10:20 ` [PATCH 2/2] docs: Introduce some hypercall page documentation Andrew Cooper
2019-05-23 10:20 ` [Xen-devel] " Andrew Cooper
2019-05-23 10:23 ` Wei Liu
2019-05-23 10:23 ` [Xen-devel] " Wei Liu
2019-05-23 10:56 ` Jan Beulich
2019-05-23 10:56 ` [Xen-devel] " Jan Beulich
2019-05-23 11:01 ` Andrew Cooper [this message]
2019-05-23 11:01 ` Andrew Cooper
2019-05-23 11:41 ` Jan Beulich
2019-05-23 11:41 ` [Xen-devel] " Jan Beulich
2019-05-23 12:02 ` Andrew Cooper
2019-05-23 12:02 ` [Xen-devel] " Andrew Cooper
2019-05-23 12:14 ` Jan Beulich
2019-05-23 12:14 ` [Xen-devel] " Jan Beulich
2019-05-29 4:10 ` [PATCH v2 " Andrew Cooper
2019-05-29 4:10 ` [Xen-devel] " Andrew Cooper
[not found] ` <EF573A6C020000F58E2C01CD@prv1-mh.provo.novell.com>
2019-05-29 8:45 ` Jan Beulich
2019-05-29 8:45 ` [Xen-devel] " Jan Beulich
2019-05-29 11:50 ` Andrew Cooper
2019-05-29 11:50 ` [Xen-devel] " Andrew Cooper
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=701d553c-20a8-7b1a-6023-35ed1008ce65@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@citrix.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).