From: Keir Fraser <keir.xen@gmail.com>
To: "Cihula, Joseph" <joseph.cihula@intel.com>,
Xen-devel <xen-devel@lists.xensource.com>
Cc: "Wang, Shane" <shane.wang@intel.com>,
"Wei, Gang" <gang.wei@intel.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: page fault in xmem_pool_alloc w/ TXT
Date: Thu, 24 Mar 2011 16:02:53 +0000 [thread overview]
Message-ID: <C9B11BAD.155A9%keir.xen@gmail.com> (raw)
In-Reply-To: <4F65016F6CB04E49BFFA15D4F7B798D90160478222@orsmsx506.amr.corp.intel.com>
Cc'ing the patch author.
-- Keir
On 24/03/2011 15:41, "Cihula, Joseph" <joseph.cihula@intel.com> wrote:
> In the latest changesets of xen-unstable, when Xen is booted with tboot/TXT,
> it gives a page fault in xmem_pool_alloc():
> ...
> (XEN) [VT-D]dmar.c:585: RMRR region: base_addr 8f305000 end_address 8f305fff
> (XEN) PCI: MCFG configuration 0: base a0000000 segment 0 buses 0 - 255
> (XEN) PCI: MCFG area at a0000000 reserved in E820
> (XEN) Xen ERST support is initialized.
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) IRQ limits: 48 GSI, 4576 MSI/MSI-X
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Early fatal page fault at e008:ffff82c48012ac66 (cr2=000000000000ec18,
> ec)
> (XEN) Stack dump: ffff83036fff9868 0000000000000060 ffff83036ffe6000
> 0000000000
> ...
>
> We have bisected this to the following commit:
> c/s 23013
> ACPI: large cleanup
>
> In some cases, entire files turned out unnecessary. Of what remains,
> move whatever possible into .init.*, and some data items into
> .data.read_mostly.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> Can someone take a look and see what got moved into .init.* that shouldn't
> have been?
>
> Joe
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-24 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 15:41 page fault in xmem_pool_alloc w/ TXT Cihula, Joseph
2011-03-24 16:02 ` Keir Fraser [this message]
2011-03-24 16:56 ` Jan Beulich
[not found] ` <4F65016F6CB04E49BFFA15D4F7B798D901607954F3@orsmsx506.amr.corp.intel.com>
2011-03-25 11:49 ` Jan Beulich
2011-03-25 15:34 ` Wei, Gang
2011-03-25 15:57 ` Cihula, Joseph
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=C9B11BAD.155A9%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@novell.com \
--cc=gang.wei@intel.com \
--cc=joseph.cihula@intel.com \
--cc=shane.wang@intel.com \
--cc=xen-devel@lists.xensource.com \
/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).