All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] x86/xen: do not identity map UNUSABLE regions in the machine E820
Date: Fri, 16 Aug 2013 18:20:12 +0100	[thread overview]
Message-ID: <520E5F4C.2080006@citrix.com> (raw)
In-Reply-To: <20130816152356.GC12047@konrad-lan.dumpdata.com>

On 16/08/13 16:23, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 16, 2013 at 03:42:55PM +0100, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> If there are UNUSABLE regions in the machine memory map, dom0 will
>> attempt to map them 1:1 which is not permitted by Xen and the kernel
>> will crash.
>>
>> There isn't anything interesting in the UNUSABLE region that the dom0
>> kernel needs access to so we can avoid making the 1:1 mapping and
>> treat it as RAM.
>>
>> We only do this for dom0, as we do not expect any domU to ever have a
>> UNUSABLE region in their pseudo-physical map.
> 
> Hm, you are going to be disappointed that this is in libxl:

The code is fine though since it only messes with UNUSABLE regions for
the initial domain. Feel free to fix up the comments and commit description.

David

  reply	other threads:[~2013-08-16 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 14:42 [PATCHv5 0/2] x86/xen: fix dom0 boot with tboot David Vrabel
2013-08-16 14:42 ` [PATCH 1/2] x86/xen: do not identity map UNUSABLE regions in the machine E820 David Vrabel
2013-08-16 15:23   ` Konrad Rzeszutek Wilk
2013-08-16 17:20     ` David Vrabel [this message]
2013-08-16 14:42 ` [PATCH 2/2] x86/xen: during early setup, only 1:1 map the ISA region David Vrabel
2013-08-16 15:25   ` Konrad Rzeszutek Wilk
2013-08-16 15:39     ` David Vrabel
2013-08-16 15:04 ` [PATCHv5 0/2] x86/xen: fix dom0 boot with tboot David Vrabel
2013-08-16 15:09   ` Ian Campbell

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=520E5F4C.2080006@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=konrad.wilk@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.