From: Wei Liu <wei.liu2@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH RFC 4/5] x86: split PVH dom0 builder to domain_build_pv.c
Date: Fri, 3 Mar 2017 13:39:24 +0000 [thread overview]
Message-ID: <20170303133924.g4jw3zaezifmhe25@citrix.com> (raw)
In-Reply-To: <20170303111639.ax5kq6oarb2fl2ih@dhcp-3-221.uk.xensource.com>
On Fri, Mar 03, 2017 at 11:16:39AM +0000, Roger Pau Monné wrote:
> On Fri, Mar 03, 2017 at 09:41:10AM +0000, Wei Liu wrote:
> > Long term we want to be able to disentangle PV and HVM code. Move the
> > PVH domain builder to a dedicated file. It will later depends on
> > CONFIG_HVM or CONFIG_PVH.
> >
> > This in turn requires exposing a few functions and variables via
> > domain_build.h.
>
> Again I would add something along the lines: "No functional changes expected".
>
> > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > ---
> > xen/arch/x86/Makefile | 1 +
> > xen/arch/x86/domain_build.c | 1068 +------------------------------------
> > xen/arch/x86/domain_build.h | 8 +
> > xen/arch/x86/domain_build_pvh.c | 1097 +++++++++++++++++++++++++++++++++++++++
>
> I would prefer that to be in arch/x86/hvm/.
>
> > diff --git a/xen/arch/x86/domain_build_pvh.c b/xen/arch/x86/domain_build_pvh.c
> > new file mode 100644
> > index 0000000000..6cd3ff2ef2
> > --- /dev/null
> > +++ b/xen/arch/x86/domain_build_pvh.c
> > @@ -0,0 +1,1097 @@
> > +/******************************************************************************
> > + * domain_build_pvh.c
> > + */
>
> Since you are already touching this, and it's mostly my code, I would rather
> prefer that you add the following header:
>
> /******************************************************************************
> * arch/x86/hvm/domain_build.c
> *
> * PVH domain builder
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Public License as published by
> * the Free Software Foundation; either version 2 of the License, or
> * (at your option) any later version.
I suggest we use the inbound licence listed in CONTRIBUTING. I think it
is GPL v2 only, without the any later version part.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-03 13:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:41 [PATCH RFC 0/5] Refactor x86 domain builder Wei Liu
2017-03-03 9:41 ` [PATCH RFC 1/5] xen: move round_pg{up,down} to pfn.h Wei Liu
2017-03-03 10:05 ` [PATCH RFC 1/5] xen: move round_pg{up, down} " Jan Beulich
2017-03-03 10:15 ` Wei Liu
2017-03-03 9:41 ` [PATCH RFC 2/5] xen: include xen/types.h in domain.h Wei Liu
2017-03-03 10:05 ` Jan Beulich
2017-03-03 9:41 ` [PATCH RFC 3/5] x86: split PV dom0 builder to domain_build_pv.c Wei Liu
2017-03-03 11:06 ` Roger Pau Monné
2017-03-03 11:15 ` Jan Beulich
2017-03-03 13:35 ` Wei Liu
2017-03-03 14:33 ` Jan Beulich
2017-03-03 14:45 ` Wei Liu
2017-03-03 14:49 ` Andrew Cooper
2017-03-03 15:15 ` Jan Beulich
2017-03-03 17:08 ` Wei Liu
2017-03-03 16:16 ` Jan Beulich
2017-03-03 9:41 ` [PATCH RFC 4/5] x86: split PVH " Wei Liu
2017-03-03 11:16 ` Roger Pau Monné
2017-03-03 13:39 ` Wei Liu [this message]
2017-03-03 15:38 ` Roger Pau Monné
2017-03-03 16:18 ` Jan Beulich
2017-03-03 9:41 ` [PATCH RFC 5/5] x86: clean up header files in domain_build.c Wei Liu
2017-03-03 16:18 ` Jan Beulich
2017-03-03 10:02 ` [PATCH RFC 0/5] Refactor x86 domain builder Jan Beulich
2017-03-03 10:56 ` Andrew Cooper
2017-03-03 11:06 ` Jan Beulich
2017-03-03 13:41 ` Wei Liu
2017-03-03 14:34 ` Jan Beulich
2017-03-03 14:45 ` Wei Liu
2017-03-03 11:06 ` 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=20170303133924.g4jw3zaezifmhe25@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@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).