From: Wei Liu <wei.liu2@citrix.com>
To: Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
george.dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
tim@xen.org, xen-devel@lists.xen.org, jbeulich@suse.com,
yang.z.zhang@intel.com, tiejun.chen@intel.com
Subject: Re: Regression in RMRRs identity mapping for PVH Dom0
Date: Thu, 24 Sep 2015 11:29:54 +0100 [thread overview]
Message-ID: <20150924102953.GA29385@zion.uk.xensource.com> (raw)
In-Reply-To: <20150923155612.GB3042@elena.ufimtseva>
Hi Elena
On Wed, Sep 23, 2015 at 11:56:12AM -0400, Elena Ufimtseva wrote:
> Hi
>
> There is a regression in RMRR patch 5ae03990c120a7b3067a52d9784c9aa72c0705a6 in
> new set_identity_p2m_entry. RMRRs are not being mapped in IOMMU for PVH Dom0.
> This causes pages faults and some long 'hang-like' delays during boot and
> device assignments.
>
> During construct_dom0, in PVH path p2m is being constructed and identity mapped
> in IOMMU. The p2m type is p2m_mmio_direct and p2m access p2m_rwx.
> New code used to map RMRRs invoked from rmrr_identity_mapping
> checks if p2m entry exists with same type and access and if yes, skips iommu
> mapping. Since there are p2m entries for pvh dom0 iomem, RMRRs are not being
> mapped in IOMMU.
>
> This debug patch attached fixes this and Ill be glad to see if there is a more elegant fix.
>
>From a release point of view, PVH Dom0 is not officially supported so I
don't consider this issue a blocker.
We can backport the proper fix to 4.6.1 if necessary, but I doubt this
is the only fix we need to make PVH Dom0 work on 4.6. Am I right?
Wei.
next prev parent reply other threads:[~2015-09-24 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 15:56 Regression in RMRRs identity mapping for PVH Dom0 Elena Ufimtseva
2015-09-24 7:17 ` Chen, Tiejun
2015-09-24 9:18 ` Tim Deegan
2015-09-24 10:31 ` Jan Beulich
2015-09-24 11:29 ` Elena Ufimtseva
2015-09-24 11:37 ` Elena Ufimtseva
2015-09-24 10:29 ` Wei Liu [this message]
2015-09-24 11:42 ` Elena Ufimtseva
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=20150924102953.GA29385@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=tiejun.chen@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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).