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>, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] x86/xen: during early setup, only 1:1 map the ISA region
Date: Fri, 16 Aug 2013 16:39:06 +0100	[thread overview]
Message-ID: <520E479A.9010004@citrix.com> (raw)
In-Reply-To: <20130816152553.GD12047@konrad-lan.dumpdata.com>

On 16/08/13 16:25, Konrad Rzeszutek Wilk wrote:
> On Fri, Aug 16, 2013 at 03:42:56PM +0100, David Vrabel wrote:
>> From: David Vrabel <david.vrabel@citrix.com>
>>
>> During early setup, when the reserved regions and MMIO holes are being
>> setup as 1:1 in the p2m, clear any mappings instead of making them 1:1
>> (execept for the ISA region which is expected to be mapped).
>>
>> This reverts a change in behaviour introduced in 3.5 by 83d51ab473dd
>> (xen/setup: update VA mapping when releasing memory during setup).
> 
> So it won't cause the original issues to reappear which is that we
> get this
> 
>     (XEN) page_alloc.c:1148:d0 Over-allocation for domain 0: 2097153 > 2097152
>     (XEN) memory.c:133:d0 Could not allocate order=0 extent: id=0 memflags=0 (0 of 17)
>     
> if we boot without dom0_mem_max ?

No, because the mapping is either updated or cleared.

David

  reply	other threads:[~2013-08-16 15:39 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
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 [this message]
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=520E479A.9010004@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.