From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Latimer Subject: Re: freemem-slack and large memory environments Date: Mon, 02 Mar 2015 15:49:45 -0700 Message-ID: <39596132.Uf7G3ZoTq8@mlatimer1.dnsdhcp.provo.novell.com> References: <4321015.nah3j6dvJq@mlatimer1.dnsdhcp.provo.novell.com> <54F46DDB020000780006505B@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54F46DDB020000780006505B@suse.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: Jan Beulich Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, wei.liu2@citrix.com, Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Monday, March 02, 2015 06:04:11 AM Jan Beulich wrote: > > Of course users could just use dom0_mem and get down with it. > > I don't think we should make this a requirement for correct > operation. Exactly. I think from a best practices perspective, dom0_mem is still the recommended approach. It just does not seem right to require that (or to expect the first domU startup to fail without it). Thanks, Mike