From: Keir Fraser <keir@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
"G.R." <firemeteor@users.sourceforge.net>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
"Jean.guyader@gmail.com" <Jean.guyader@gmail.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion.
Date: Thu, 20 Dec 2012 13:03:31 +0000 [thread overview]
Message-ID: <CCF8BD23.561A3%keir@xen.org> (raw)
In-Reply-To: <1356000101.26722.41.camel@zakaz.uk.xensource.com>
On 20/12/2012 10:41, "Ian Campbell" <Ian.Campbell@citrix.com> 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. <firemeteor@users.sourceforge.net>
>> 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
next prev parent reply other threads:[~2012-12-20 13:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 3:52 [PATCH] hvmloader / qemu-xen: Getting rid of resource conflict for OpRegion G.R.
2012-12-20 3:56 ` G.R.
2012-12-20 10:41 ` Ian Campbell
2012-12-20 13:03 ` Keir Fraser [this message]
2012-12-20 13:31 ` G.R.
2012-12-20 14:19 ` Keir Fraser
2012-12-20 15:06 ` G.R.
2012-12-20 18:27 ` Ross Philipson
2012-12-21 3:59 ` G.R.
2012-12-21 15:55 ` Ross Philipson
2012-12-21 16:49 ` G.R.
2012-12-21 17:03 ` Ross Philipson
2012-12-21 17:26 ` Ross Philipson
2012-12-23 6:11 ` G.R.
2013-01-02 16:34 ` Ross Philipson
2013-01-04 7:25 ` G.R.
2013-01-09 15:34 ` G.R.
2013-01-09 16:36 ` Ross Philipson
2013-01-10 10:27 ` G.R.
2013-01-10 13:40 ` Ross Philipson
2013-01-10 16:29 ` G.R.
2013-01-14 16:01 ` Ross Philipson
2013-01-15 16:44 ` G.R.
2012-12-20 19:44 ` Jean Guyader
2012-12-20 19:50 ` Ian Campbell
2012-12-21 3:51 ` G.R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CCF8BD23.561A3%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Jean.guyader@gmail.com \
--cc=firemeteor@users.sourceforge.net \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).