From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion. Date: Thu, 20 Dec 2012 13:03:31 +0000 Message-ID: References: <1356000101.26722.41.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1356000101.26722.41.camel@zakaz.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 Campbell , "G.R." Cc: Stefano Stabellini , "Jean.guyader@gmail.com" , xen-devel List-Id: xen-devel@lists.xenproject.org On 20/12/2012 10:41, "Ian Campbell" wrote: > Adding our qemu maintainer. > > On Thu, 2012-12-20 at 03:56 +0000, G.R. wrote: >> Switch to a new address that can reach to Jean. >> >> On Thu, Dec 20, 2012 at 11:52 AM, G.R. >> wrote: >>> This is hvmloader part of the change that gets rid of the resource >>> conflict warning in the guest kernel. >>> The OpRegion may not always be page aligned. > > Is it worth detecting this and allocating 2 or 3 pages as required? > > The OpRegion is always 8096 bytes? (two pages, but not necessarily > aligned)? > > Do we need to worry about what is in the "slop" at either end of a 3 > page region containing this? If they are sensitive registers then we may > have a problem. In the hvmloader patch it is not worth it I think, one extra page of memory hole is hardly a scarce resource. I don't know whether the qemu side is accurate enough. If the region is 8096 bytes then it is not necessarily the case that an unaligned start address means we need three pages mapped. -- Keir > Ian. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel