From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH v2 2/2] xl: Add mem_set_enforce_limit option to xl.conf file Date: Tue, 26 Mar 2013 09:10:53 -0400 Message-ID: <20130326131053.GA18215@phenom.dumpdata.com> References: <1363873979-6087-1-git-send-email-daniel.kiper@oracle.com> <1363873979-6087-3-git-send-email-daniel.kiper@oracle.com> <20816.30750.731502.73036@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20816.30750.731502.73036@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: Daniel Kiper , "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Mon, Mar 25, 2013 at 04:15:26PM +0000, Ian Jackson wrote: > Daniel Kiper writes ("[PATCH v2 2/2] xl: Add mem_set_enforce_limit option to xl.conf file"): > > Add mem_set_enforce_limit option to xl.conf file. > > It gives a chance to align xl mem-set behavior > > to xm mem-set behavior. Default xl mem-set > > behavior is not changed. > > Should this be a per-domain config option ? I confess I don't > understand the usage model very well but it would seem that enforcing > against some guests but not others would be a sensible otpion. This option is to provide a mechanism to fallback to xend behavior. > > Ian. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >