All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: xen-devel@lists.xen.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Subject: [PATCHv5 0/2] x86/xen: fix dom0 boot with tboot
Date: Fri, 16 Aug 2013 15:42:54 +0100	[thread overview]
Message-ID: <1376664176-27535-1-git-send-email-david.vrabel@citrix.com> (raw)

The first patch (for 3.11 and which should be considered for stable),
fixes boot failures caused by UNUSABLE regions in the e820 machine
memory map.  This typically occurs if tboot is used.

The second patch (for 3.12) is clean up some an inadvertant change to
the mappings setup during early init, as introduced in 3.5.  There is
no need for this to be backported though.

Changes in v5:
- Use the original approach of removing UNUSABLE regions as the
  previous fix did not work when backported to older kernels.

Changes in v4:
- Extend 1:1 mapping region to cover 0 - 1MiB. find_ibft_region()
  scans from 512 KiB and if this overlapped with a reserved region it
  would crash.

Changes in v3:
- Avoid the 1:1 mapping (except for the ISA region) by the early setup
  instead of removing UNUSABLE regions.

Changes in v2:
- Refactor getting the correct memory map.

David

             reply	other threads:[~2013-08-16 14:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 14:42 David Vrabel [this message]
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
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=1376664176-27535-1-git-send-email-david.vrabel@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@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.