From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v2 2/4] x86: split PV dom0 builder to pv/dom0_builder.c
Date: Thu, 16 Mar 2017 18:15:01 +0000 [thread overview]
Message-ID: <632357f9-10df-8b4e-a953-c5f236b3e29b@citrix.com> (raw)
In-Reply-To: <20170316181208.q4pznggmpum23n56@dhcp-3-128.uk.xensource.com>
On 16/03/17 18:12, Roger Pau Monné wrote:
> On Thu, Mar 16, 2017 at 05:54:56PM +0000, Wei Liu wrote:
> [...]
>> + /*
>> + * PVH Fixme: XENFEAT_supervisor_mode_kernel has been reused in PVH with a
>> + * different meaning.
> Crap, I've forgot to remove this PVH fixme!
And
andrewcoop@andrewcoop:/local/xen.git/xen$ git grep -l has_hvm_container
-- :/
../docs/designs/dmop.markdown
include/xen/sched.h
if you are feeling like fixing up other stray bits :)
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-16 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 17:54 [PATCH v2 0/4] Refactor x86 dom0 builder Wei Liu
2017-03-16 17:54 ` [PATCH v2 1/4] x86: rename domain_build.c to dom0_build.c Wei Liu
2017-03-16 18:00 ` Andrew Cooper
2017-03-16 17:54 ` [PATCH v2 2/4] x86: split PV dom0 builder to pv/dom0_builder.c Wei Liu
2017-03-16 18:12 ` Roger Pau Monné
2017-03-16 18:14 ` Wei Liu
2017-03-16 18:15 ` Andrew Cooper [this message]
2017-03-16 18:48 ` Wei Liu
2017-03-17 11:15 ` Andrew Cooper
2017-03-17 11:18 ` Wei Liu
2017-03-20 10:40 ` Jan Beulich
2017-03-20 13:10 ` Wei Liu
2017-03-20 13:35 ` Jan Beulich
2017-03-16 17:54 ` [PATCH v2 3/4] x86: split PVH dom0 builder to hvm/dom0_build.c Wei Liu
2017-03-16 18:16 ` Roger Pau Monné
2017-03-16 18:21 ` Wei Liu
2017-03-17 10:00 ` Roger Pau Monné
2017-03-16 17:54 ` [PATCH v2 4/4] x86: clean up header files in dom0_build.c Wei Liu
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=632357f9-10df-8b4e-a953-c5f236b3e29b@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.com \
--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).