From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Requesting for freeze exception for RMRR Date: Mon, 13 Jul 2015 09:11:18 +0100 Message-ID: <55A38EC6020000780008FF73@mail.emea.novell.com> References: <55A35B5E.3000805@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55A35B5E.3000805@intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "wei.liu2@citrix.com" , Tiejun Chen Cc: Kevin , "ian.campbell@citrix.com" , George Dunlap , Andrew Cooper , "ian.jackson@eu.citrix.com" , Yong Y Wang , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >>> On 13.07.15 at 08:31, wrote: > 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. I think this should read "Our policy intends to make sure ...", making more clear that there is a risk here (supported by the history of the series). Jan