xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: fixed location of share info page in HVM guests
Date: Tue, 28 Aug 2012 12:40:41 +0100	[thread overview]
Message-ID: <CC626CC9.3CFA1%keir.xen@gmail.com> (raw)
In-Reply-To: <20120828082302.GA27309@aepfle.de>

On 28/08/2012 09:23, "Olaf Hering" <olaf@aepfle.de> wrote:

> On Tue, Aug 28, Keir Fraser wrote:
> 
>> How about we guarantee that guests can use the 1MB in address range
>> 0xFED00000-0xFEDFFFFF for whatever mappings they like, guaranteed unused (or
>> at least, mapped with nothing useful) when guest kernel starts?
>> 
>> This is already, and has always been, the case. But we can etch it in stone
>> quite easily. :)
> 
> 0xFED00000UL is appearently the hpet base adress. But if there is room
> after that, then lets use that. However, I'm not familiar with these
> things. Should the area appear in the E820 map as reserverd? If so,
> where is the code which configures the guests E820 map?

Okay, that was a bit too clever, trying to hide between IOAPIC and LAPIC
pages. How about a bit lower in memory -- FE700000-FE7FFFFF?

Everything in range FC000000-FFFFFFFF should already be marked
E820_RESERVED. You can test that, and also see
tools/firmware/hvmloader/e820.c:build_e820_table() (and note that
RESERVED_MEMBASE == FC000000).

Can document in hvmloader/config.h and have mem_alloc() test against it
rather than hvm_info->reserved_mem_pgstart.

 -- Keir

> Olaf

  reply	other threads:[~2012-08-28 11:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 17:55 fixed location of share info page in HVM guests Olaf Hering
2012-08-27 18:10 ` Keir Fraser
2012-08-27 21:32   ` Olaf Hering
2012-08-27 21:51     ` Keir Fraser
2012-08-27 21:56       ` Olaf Hering
2012-08-28  0:13         ` Keir Fraser
2012-08-28  8:23           ` Olaf Hering
2012-08-28 11:40             ` Keir Fraser [this message]
2012-08-28 12:42               ` Olaf Hering
2012-08-28 13:35                 ` Keir Fraser
2012-08-31 23:43                   ` Konrad Rzeszutek Wilk
2012-10-23 19:49                     ` Olaf Hering
2012-10-24  7:31                       ` Jan Beulich
2012-10-24 14:54                         ` Olaf Hering
2012-10-22 18:50               ` Olaf Hering
2012-10-22 12:15                 ` Keir Fraser
2012-10-23  7:34                 ` Jan Beulich
2012-10-23 20:27                   ` Olaf Hering

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=CC626CC9.3CFA1%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=olaf@aepfle.de \
    --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).