From: Olaf Hering <olaf@aepfle.de>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com
Subject: Re: xenpaging crashes xen in is_iomem_page()
Date: Tue, 27 Jul 2010 17:20:45 +0200 [thread overview]
Message-ID: <20100727152045.GA20188@aepfle.de> (raw)
In-Reply-To: <AANLkTimCNX9Cnr8cOpvOw=oDgWObNvXYbXP6=9ZxpCDc@mail.gmail.com>
On Mon, Jul 26, Patrick Colp wrote:
> I've not seen this error before. Does your computer have EPT support?
Now I got another system with X5550 cpu, i7 based.
x86info reports:
...
CPU #8
EFamily: 0 EModel: 1 Family: 6 Model: 26 Stepping: 5
CPU Model: Core i7 (Nehalem)
Processor name string: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz
And it still crashes this way.
XEN reports this during boot:
...
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Brought up 8 CPUs
...
So, is xenpaging really working for you?
Olaf
next prev parent reply other threads:[~2010-07-27 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 11:58 xenpaging crashes xen in is_iomem_page() Olaf Hering
2010-07-26 13:15 ` Patrick Colp
2010-07-26 14:08 ` Olaf Hering
2010-07-26 14:39 ` Patrick Colp
2010-07-26 14:58 ` Tim Deegan
2010-07-26 15:23 ` Patrick Colp
2010-07-27 15:20 ` Olaf Hering [this message]
2010-07-27 15:46 ` Patrick Colp
2010-07-27 18:25 ` Olaf Hering
2010-07-27 18:39 ` Patrick Colp
2010-07-28 15:26 ` Olaf Hering
2010-07-28 16:22 ` Patrick Colp
2010-08-06 11:16 ` Olaf Hering
2010-08-09 13:30 ` Patrick Colp
2010-08-09 17:39 ` Olaf Hering
2010-08-09 18:23 ` Patrick Colp
2010-08-10 14:19 ` Olaf Hering
2010-08-10 15:02 ` Patrick Colp
2010-08-10 15:06 ` 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=20100727152045.GA20188@aepfle.de \
--to=olaf@aepfle.de \
--cc=pjcolp@cs.ubc.ca \
--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).