From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [v4][PATCH 12/19] tools/libxl: passes rdm reservation policy Date: Tue, 30 Jun 2015 10:14:59 +0800 Message-ID: <5591FBA3.9070501@intel.com> References: <1435053450-25131-1-git-send-email-tiejun.chen@intel.com> <1435053450-25131-13-git-send-email-tiejun.chen@intel.com> <21899.62720.119875.764677@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21899.62720.119875.764677@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Stefano Stabellini , Wei Liu , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org >> +B is about how to handle conflict between reserving reserved device >> +memory and guest address space. "strict" means an unsolved conflict leads to >> +immediate VM crash, while "relaxed" allows VM moving forward with a warning >> +message thrown out. Here "strict" is default. > > Surely it would be better to reject the attach attempt rather than > crashing the domain. Yes, indeed we just fail to create this VM in the case of runtime, or to hotplug this associated device in the case of hotplug. I would rephrase this somewhere, the here just introduce a reference like this as Campbell said to me, +B specifies how to handle conflicts between reserved device memory +space and guest address space. This is same as "reserve" option to the rdm +option, please see L. + > > Also, again, this text is not really user-focused. It needs to > explain what the risks of using `relaxed' are (or what other checks or > countermeasures the admin should use before setting `relaxed'). > After make this referring to other place, please see this on another email. Thanks Tiejun