xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Kevin <kevin.tian@intel.com>
Cc: "Wang, Yong Y" <yong.y.wang@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Requesting for freeze exception for RMRR
Date: Mon, 13 Jul 2015 14:31:58 +0800	[thread overview]
Message-ID: <55A35B5E.3000805@intel.com> (raw)

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
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
Y		N	[v7][PATCH 07/16] hvmloader/e820: construct guest e820 table
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
Y		Y	[v7][PATCH 16/16] tools: parse to enable new rdm policy parameters	

Note Jackson and Campbell also raised some comments to improve current 
codes.

2. explain why it needs to be in this release (benefits).

RMRR mechanism was broken for a long time and this makes VM always face 
security issues. In addition, those associated devices can't be passed 
through to VM and even result in VM crashes.

3. explain why it doesn't break things (risks).

Our policy makes sure that system will work in the original way by 
default as without the RMRR patches. And especially, this series just 
impacts those platforms which have RMRR.

4. CC relevant maintainers and release manager.
Done

Cheers,
Tiejun

             reply	other threads:[~2015-07-13  6:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  6:31 Chen, Tiejun [this message]
2015-07-13  8:11 ` Requesting for freeze exception for RMRR 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
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=55A35B5E.3000805@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=kevin.tian@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).