From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.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>,
roger.pau@citrix.com
Subject: Re: [Draft C] Boot ABI for HVM guests without a device-model
Date: Fri, 4 Sep 2015 17:10:25 +0100 [thread overview]
Message-ID: <1441383025.25589.8.camel@citrix.com> (raw)
In-Reply-To: <55E9DC88020000780009FDFD@prv-mh.provo.novell.com>
On Fri, 2015-09-04 at 10:01 -0600, Jan Beulich wrote:
> >
> > > > On 04.09.15 at 17:26, <ian.campbell@citrix.com> wrote:
> > On Fri, 2015-09-04 at 09:21 -0600, Jan Beulich wrote:
> > > > > > On 04.09.15 at 16:31, <roger.pau@citrix.com> wrote:
> > > > El 04/09/15 a les 16.08, Jan Beulich ha escrit:
> > > > > > > > On 04.09.15 at 14:11, <roger.pau@citrix.com> wrote:
> > > > > > AP startup
> > > > > > ==========
> > > > > >
> > > > > > AP startup is performed using hypercalls. The following VCPU
> > > > > > operations
> > > > > > are used in order to bring up secondary vCPUs:
> > > > > >
> > > > > > * VCPUOP_initialise is used to set the initial state of the
> > > > > > vCPU.
> > > > > > The
> > > > > > argument passed to the hypercall must be of the type > > > >
> > > > > >
> > vcpu_hvm_context.
> > > > >
> > > > > VCPUOP_initialise takes a struct vcpu_guest_context; I don't
> > > > > think
> > > > > we can or should change that.
> > > >
> > > > Didn't we agree that vcpu_guest_context was not suitable for
> > > > HVM/PVH
> > > > guests?
> > >
> > > Yes we did.
> > >
> > > > Patch 24 of my HVM-without-dm series already introduces this new
> > > > structure and the necessary helpers.
> > >
> > > I didn't look at most of the series yet (despite it already being at
> > > v6;
> > > I'm sorry, I just didn't get around so far). But I think you agree
> > > that
> > > we can't just change an existing hypercall. Iirc along with agreeing
> > > on vcpu_guest_context not being suitable we also agreed that this
> > > will need to be a new sub-op, and I wondered whether calling it
> > > VCPUOP_initialize would be too subtle.
> >
> > You mean literally only s/s/z/?
>
> Indeed ;-)
>
> > In which case, yes, far far to subtle.
>
> I was afraid I would get feedback like this (and I was surprised I
> didn't already when I first suggested this).
I think even if I'd have seen it the first time I'd have thought you were
joking...
Ian.
next prev parent reply other threads:[~2015-09-04 16:17 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 [this message]
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é
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=1441383025.25589.8.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=roger.pau@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.