From: Ian Campbell <ian.campbell@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
wei.liu2@citrix.com
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v4.2] libxc: Defer initialization of start_page for HVM guests
Date: Fri, 8 Jan 2016 14:31:22 +0000 [thread overview]
Message-ID: <1452263482.29416.40.camel@citrix.com> (raw)
In-Reply-To: <568FC56F.3050209@oracle.com>
On Fri, 2016-01-08 at 09:19 -0500, Boris Ostrovsky wrote:
> index 2460818..cac4698 100644
> > > --- a/tools/libxc/include/xc_dom.h
> > > +++ b/tools/libxc/include/xc_dom.h
> > > @@ -71,6 +71,7 @@ struct xc_dom_image {
> > >
> > > /* arguments and parameters */
> > > char *cmdline;
> > > + size_t cmdline_size;
> > > uint32_t f_requested[XENFEAT_NR_SUBMAPS];
> > >
> > > /* info from (elf) kernel image */
> > > @@ -91,6 +92,7 @@ struct xc_dom_image {
> > > struct xc_dom_seg p2m_seg;
> > > struct xc_dom_seg pgtables_seg;
> > > struct xc_dom_seg devicetree_seg;
> > > + struct xc_dom_seg start_info_seg; /* HVMlite only */
> > Instead of adding HVM specific members here, you could make use of
> > dom.arch_private and use just a local structure defined in
> > xc_dom_x86.c.
>
> I did consider this but since we already keep type-specific segments in
> this structure (e.g. p2m_seg) decided to add an explicit segment for
> HVMlite.
>
> Besides, I think to properly use it we'd need to add an arch hook and
> IMHO it's not worth the trouble in this case.
Agreed, it is at best a potential future cleanup.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-08 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 22:19 [PATCH v4.2] libxc: Defer initialization of start_page for HVM guests Boris Ostrovsky
2016-01-08 4:57 ` Juergen Gross
2016-01-08 14:19 ` Boris Ostrovsky
2016-01-08 14:30 ` Juergen Gross
2016-01-08 14:53 ` Boris Ostrovsky
2016-01-08 15:11 ` Ian Campbell
2016-01-08 15:19 ` Boris Ostrovsky
2016-01-08 15:24 ` Roger Pau Monné
2016-01-19 15:02 ` Boris Ostrovsky
2016-01-19 15:13 ` Ian Campbell
2016-01-19 16:48 ` Ian Campbell
2016-01-08 14:31 ` Ian Campbell [this message]
2016-01-08 9:58 ` Ian Campbell
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=1452263482.29416.40.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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 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).