From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: yang.z.zhang@intel.com,
xen-devel <xen-devel@lists.xenproject.org>,
kevin.tian@intel.com
Subject: Re: Shared page tables between ETP and IOMMU issue
Date: Thu, 26 Feb 2015 17:29:36 +0100 [thread overview]
Message-ID: <54EF49F0.3080000@citrix.com> (raw)
In-Reply-To: <54EF507902000078000642F7@mail.emea.novell.com>
El 26/02/15 a les 16.57, Jan Beulich ha escrit:
>>>> On 26.02.15 at 16:45, <roger.pau@citrix.com> wrote:
>> While testing PVH Dom0 support on a newer Core i3-5010U I've found that
>> sharing the page tables between EPT and the IOMMUs don't work. Booting
>> with iommu=no-sharept solves the problem, but I'm unsure what causes
>> this issue.
>
> Is FreeBSD fiddling with its own memory map in some way? It's rather
> surprising to see not just an occasional fault, but many of them, and
> with L2 or even L3 entries not present.
No, FreeBSD doesn't touch the physical memory map at all. No ballooning
or anything like that.
> I.e. if it's not the OS
> requesting re-arrangements, I would suppose table setup itself is
> screwed up in some way. In the end - knowing the valid GFN range
> for the guest - you may want to monitor/log how tables get created
> and whether (and if so by whom) later some of the entries get
> zapped.
OK, I will try to take a look. All those faults come from physical
memory ranges that are supposed to be usable, and in fact the CPU seems
to be able to read/write from them without problems, or else the guest
would have crashed much more early. Regarding sharing the page tables
between EPT and the IOMMU, is there some bit that needs to be set in the
ept entry in order to mark a page as available by the IOMMU?
Roger.
next prev parent reply other threads:[~2015-02-26 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 15:45 Shared page tables between ETP and IOMMU issue Roger Pau Monné
2015-02-26 15:57 ` Jan Beulich
2015-02-26 16:29 ` Roger Pau Monné [this message]
2015-02-26 16:43 ` Jan Beulich
2015-02-26 18:02 ` Roger Pau Monné
2015-02-26 19:28 ` Konrad Rzeszutek Wilk
2015-02-26 19:34 ` Roger Pau Monné
2015-02-26 19:31 ` Roger Pau Monné
2015-02-26 22:17 ` Elena Ufimtseva
2015-02-27 8:16 ` Jan Beulich
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=54EF49F0.3080000@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.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 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.