From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: (v2) Design proposal for RMRR fix Date: Mon, 12 Jan 2015 11:37:11 +0000 Message-ID: <54B3BFF70200007800053ADC@mail.emea.novell.com> References: <54AE9A2F0200007800052ACF@mail.emea.novell.com> <54AFAB90020000780005303C@mail.emea.novell.com> <54AFBCE502000078000530F3@mail.emea.novell.com> <54B3A2D602000078000538A2@mail.emea.novell.com> <54B3A71002000078000538E1@mail.emea.novell.com> <54B3AB380200007800053917@mail.emea.novell.com> <54B3AE8802000078000539B7@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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: Kevin Tian Cc: "wei.liu2@citrix.com" , "ian.campbell@citrix.com" , "stefano.stabellini@eu.citrix.com" , "tim@xen.org" , "ian.jackson@eu.citrix.com" , "xen-devel@lists.xen.org" , Yang Z Zhang , Tiejun Chen List-Id: xen-devel@lists.xenproject.org >>> On 12.01.15 at 12:22, wrote: >> From: Jan Beulich [mailto:JBeulich@suse.com] >> Sent: Monday, January 12, 2015 6:23 PM >> One of my main problems with all you recent argumentation here >> is the arbitrary use of the 1Gb boundary - there's nothing special >> in this discussion with where the boundary is. Everything revolves >> around the (undue) effect of report-all on domains not needing all >> of the ranges found on the host. >> > > I'm not sure which part of my argument is not clear here. report-all > would be a problem here only if we want to fix all the conflictions > (then pulling unnecessary devices increases the confliction possibility) > in the domain builder. but if we only fix reasonable ones (e.g. >3GB) > while warn other conflictions (e.g. <3G) in domain builder (let later > assignment path to actually fail if confliction does matter), And have no way for the user to (securely) avoid that failure. Plus the definition of "reasonable" here is of course going to be arbitrary. Jan > then we > don't need to solve all conflictions in domain builder (if say 1G example > fixing it may instead reduce lowmem greatly) and then report-all > may just add more warnings than report-sel for unused devices. > > Thanks > Kevin