From: "Jan Beulich" <JBeulich@suse.com>
To: "wei.liu2@citrix.com" <wei.liu2@citrix.com>,
Tiejun Chen <tiejun.chen@intel.com>
Cc: Kevin <kevin.tian@intel.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
Yong Y Wang <yong.y.wang@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Requesting for freeze exception for RMRR
Date: Mon, 13 Jul 2015 14:38:48 +0100 [thread overview]
Message-ID: <55A3DB88020000780009035D@mail.emea.novell.com> (raw)
In-Reply-To: <55A35B5E.3000805@intel.com>
>>> On 13.07.15 at 08:31, <tiejun.chen@intel.com> wrote:
> Hi Wei,
>
> Here I'm trying to request the freeze exception for RMRR.
>
> 1. clarify the state of patch series / feature.
>
> Reviewed Acked RMRR series v7
> Y Y [v7][PATCH 01/16] xen: introduce XENMEM_reserved_device_memory_map
> Y Y [v7][PATCH 02/16] xen/vtd: create RMRR mapping
> Y N [v7][PATCH 03/16] xen/passthrough: extend hypercall to support rdm
> reservation policy
I can't seem to find any such Reviewed-by on the list (and the patch
itself doesn't carry one either).
> Y Y [v7][PATCH 04/16] xen: enable XENMEM_memory_map in hvm
> Y N [v7][PATCH 05/16] hvmloader: get guest memory map into memory_map[]
> Y N [v7][PATCH 06/16] hvmloader/pci: skip reserved ranges
Same here.
> Y N [v7][PATCH 07/16] hvmloader/e820: construct guest e820 table
And again.
> Y Y [v7][PATCH 08/16] tools/libxc: Expose new hypercall
> xc_reserved_device_memory_map
> Y Y [v7][PATCH 09/16] tools: extend xc_assign_device() to support rdm
> reservation policy
> Y Y [v7][PATCH 10/16] tools: introduce some new parameters to set rdm
> policy
> Y Y [v7][PATCH 11/16] tools/libxl: detect and avoid conflicts with RDM
> Y Y [v7][PATCH 12/16] tools: introduce a new parameter to set a
> predefined rdm boundary
> Y Y [v7][PATCH 13/16] libxl: construct e820 map with RDM information
> for HVM guest
> Y Y [v7][PATCH 14/16] xen/vtd: enable USB device assignment
> Y Y [v7][PATCH 15/16] xen/vtd: prevent from assign the device with
> shared rmrr
And yet again for these two. Please avoid giving a false impression
of the state of the series to the release manager (and others).
Jan
next prev parent reply other threads:[~2015-07-13 13:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:31 Requesting for freeze exception for RMRR Chen, Tiejun
2015-07-13 8:11 ` Jan Beulich
2015-07-13 11:41 ` Wei Liu
2015-07-14 1:27 ` Chen, Tiejun
2015-07-14 9:29 ` Wei Liu
2015-07-17 1:16 ` Chen, Tiejun
2015-07-17 9:17 ` Wei Liu
2015-07-17 9:24 ` Chen, Tiejun
2015-07-17 9:30 ` Wei Liu
2015-07-17 13:21 ` Wei Liu
2015-07-17 13:43 ` Jan Beulich
2015-07-17 14:01 ` Wei Liu
2015-07-17 14:33 ` Chen, Tiejun
2015-07-17 15:11 ` Andrew Cooper
2015-07-17 15:26 ` Chen, Tiejun
2015-07-17 15:32 ` Wei Liu
2015-07-17 15:37 ` Chen, Tiejun
2015-07-20 1:14 ` Tian, Kevin
2015-07-13 13:38 ` Jan Beulich [this message]
2015-07-14 0:26 ` Chen, Tiejun
2015-07-14 9:18 ` Jan Beulich
2015-07-14 9:25 ` Ian Campbell
2015-07-14 9:36 ` Jan Beulich
2015-07-14 9:27 ` Chen, Tiejun
2015-07-14 9:38 ` Jan Beulich
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=55A3DB88020000780009035D@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=tiejun.chen@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yong.y.wang@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).