From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Paul Durrant <paul.durrant@citrix.com>,
Zhiyuan Lv <zhiyuan.lv@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v3 1/3] x86/ioreq server(patch for 4.7): Rename p2m_mmio_write_dm to p2m_ioreq_server.
Date: Mon, 25 Apr 2016 08:14:11 -0600 [thread overview]
Message-ID: <571E425302000078000E5621@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CAFLBxZavhPdTmxjR-prgiJY9VALjQg10KjqpAn3N5mhuC+XpmQ@mail.gmail.com>
>>> On 25.04.16 at 15:39, <George.Dunlap@eu.citrix.com> wrote:
> On Mon, Apr 25, 2016 at 11:35 AM, Yu Zhang <yu.c.zhang@linux.intel.com> wrote:
>> --- a/xen/include/public/hvm/hvm_op.h
>> +++ b/xen/include/public/hvm/hvm_op.h
>> @@ -83,7 +83,13 @@ typedef enum {
>> HVMMEM_ram_rw, /* Normal read/write guest RAM */
>> HVMMEM_ram_ro, /* Read-only; writes are discarded */
>> HVMMEM_mmio_dm, /* Reads and write go to the device model */
>> - HVMMEM_mmio_write_dm /* Read-only; writes go to the device model */
>> +#if __XEN_INTERFACE_VERSION__ < 0x00040700
>> + HVMMEM_mmio_write_dm, /* Read-only; writes go to the device model */
>> +#else
>> + HVMMEM_unused, /* Placeholder; setting memory to this type
>> + will fail for code after 4.7.0 */
>> +#endif
>> + HVMMEM_ioreq_server
>
> Also, I don't think we've had a convincing argument for why this patch
> needs to be in 4.7. The p2m name changes are internal only, and so
> don't need to be made at all; and the old functionality will work as
> well as it ever did. Furthermore, the whole reason we're in this
> situation is that we checked in a publicly-visible change to the
> interface before it was properly ready; I think we should avoid making
> the same mistake this time.
Good point.
> So personally I'd just leave this patch entirely for 4.8; but if Paul
> and/or Jan have strong opinions, then I would say check in only a
> patch to do the #if/#else/#endif, and leave both the p2m type changes
> and the new HVMMEM_ioreq_server enum for when the 4.8 development
> window opens.
Doing that alone would break the build - it would need to be a
little more than that.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-25 14:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:35 [PATCH v3 0/3] x86/ioreq server: Introduce HVMMEM_ioreq_server mem type Yu Zhang
2016-04-25 10:35 ` [PATCH v3 1/3] x86/ioreq server(patch for 4.7): Rename p2m_mmio_write_dm to p2m_ioreq_server Yu Zhang
2016-04-25 12:12 ` Jan Beulich
2016-04-25 13:30 ` Wei Liu
2016-04-25 13:39 ` George Dunlap
2016-04-25 14:01 ` Paul Durrant
2016-04-25 14:15 ` George Dunlap
2016-04-25 14:16 ` Jan Beulich
2016-04-25 14:19 ` Paul Durrant
2016-04-25 14:28 ` George Dunlap
2016-04-25 14:34 ` Paul Durrant
2016-04-25 15:21 ` Yu, Zhang
2016-04-25 15:29 ` Paul Durrant
2016-04-25 15:38 ` Jan Beulich
2016-04-25 15:53 ` Yu, Zhang
2016-04-25 16:15 ` George Dunlap
2016-04-25 16:20 ` Yu, Zhang
2016-04-25 17:01 ` Paul Durrant
2016-04-26 8:23 ` Yu, Zhang
2016-04-26 8:33 ` Paul Durrant
2016-04-27 14:12 ` George Dunlap
2016-04-27 14:42 ` Paul Durrant
2016-04-28 2:47 ` Yu, Zhang
2016-04-28 7:14 ` Paul Durrant
2016-04-28 7:07 ` Yu, Zhang
2016-04-28 10:02 ` Jan Beulich
2016-04-28 10:43 ` Paul Durrant
2016-04-27 14:47 ` Wei Liu
2016-04-25 15:49 ` Yu, Zhang
2016-04-25 14:14 ` Jan Beulich [this message]
2016-04-25 10:35 ` [PATCH v3 2/3] x86/ioreq server: Add new functions to get/set memory types Yu Zhang
2016-04-26 10:53 ` Wei Liu
2016-04-27 9:11 ` Yu, Zhang
2016-04-25 10:35 ` [PATCH v3 3/3] x86/ioreq server: Add HVMOP to map guest ram with p2m_ioreq_server to an ioreq server Yu Zhang
2016-04-25 12:36 ` Paul Durrant
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=571E425302000078000E5621@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=paul.durrant@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yu.c.zhang@linux.intel.com \
--cc=zhiyuan.lv@intel.com \
/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).