From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Ian Campbell <ian.campbell@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Draft C] Boot ABI for HVM guests without a device-model
Date: Tue, 15 Sep 2015 09:08:37 +0200 [thread overview]
Message-ID: <55F7C3F5.1020609@citrix.com> (raw)
In-Reply-To: <55ED7D7B02000078000A0522@prv-mh.provo.novell.com>
El 07/09/15 a les 12.05, Jan Beulich ha escrit:
>>>> On 07.09.15 at 11:34, <roger.pau@citrix.com> wrote:
>> So AFAICS we have 3 options:
>>
>> 1. Overload VCPUOP_initialise like it's done in the current series (v6).
>> For PV guests the hypercall parameter is of type vcpu_guest_context,
>> while for HVM guests the parameter is of type vcpu_hvm_context.
>>
>> 2. Create a new hypercall (VCPUOP_hvm_initialise) only available to HVM
>> guests, that only allows vcpu_hvm_context as a parameter.
>>
>> 3. Deprecate current VCPUOP_initialise, introduce a new
>> VCPUOP_initialise, that takes the following parameter:
>>
>> union vcpu_context {
>> struct vcpu_guest_context pv_ctx;
>> struct vcpu_hvm_context hvm_ctx;
>> };
>>
>> TBH, I don't have an opinion between 2 and 3, but I would like to get a
>> consensus before I start implementing any of those.
>
> Let me first take a look at how your implementation of 1 looks like.
Ping?
next prev parent reply other threads:[~2015-09-15 7:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 12:11 [Draft C] Boot ABI for HVM guests without a device-model Roger Pau Monné
2015-09-04 14:08 ` Jan Beulich
2015-09-04 14:31 ` Roger Pau Monné
2015-09-04 15:17 ` Jan Beulich
2015-09-04 15:21 ` Jan Beulich
2015-09-04 15:26 ` Ian Campbell
2015-09-04 16:01 ` Jan Beulich
2015-09-04 16:10 ` Ian Campbell
2015-09-04 15:47 ` Roger Pau Monné
2015-09-04 16:03 ` Jan Beulich
2015-09-04 16:09 ` Roger Pau Monné
2015-09-04 16:12 ` Ian Campbell
2015-09-07 9:34 ` Roger Pau Monné
2015-09-07 10:05 ` Jan Beulich
2015-09-15 7:08 ` Roger Pau Monné [this message]
2015-09-15 7:14 ` Jan Beulich
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=55F7C3F5.1020609@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=tim@xen.org \
--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 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.