From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <Ian.Jackson@eu.citrix.com>,
Julien Grall <julien.grall@arm.com>
Subject: Re: [PATCH] IOMMU/x86: per-domain control structure is not HVM-specific
Date: Tue, 03 May 2016 03:59:06 -0600 [thread overview]
Message-ID: <5728928A02000078000E7EE9@prv-mh.provo.novell.com> (raw)
In-Reply-To: <57287103.8060300@citrix.com>
>>> On 03.05.16 at 11:36, <andrew.cooper3@citrix.com> wrote:
> On 02/05/16 13:55, Jan Beulich wrote:
>> ... and hence should not live in the HVM part of the PV/HVM union. In
>> fact it's not even architecture specific (there already is a per-arch
>> extension type to it), so it gets moved out right to common struct
>> domain.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Yikes - this really does need fixing ASAP.
The more interesting question here is how to deal with the stable
trees: The patch, due to its size, doesn't really lend itself to
backporting. Yet the alternative (mentioned in a remark in the
original submission) would be pretty clumsy too.
Opinions?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-03 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 12:55 [PATCH] IOMMU/x86: per-domain control structure is not HVM-specific Jan Beulich
2016-05-03 9:36 ` Andrew Cooper
2016-05-03 9:59 ` Jan Beulich [this message]
2016-05-03 10:18 ` Andrew Cooper
2016-05-03 10:34 ` George Dunlap
2016-05-03 12:47 ` Julien Grall
2016-05-03 13:37 ` 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=5728928A02000078000E7EE9@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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).