From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/1] xen:vtd: missing RMRR mapping while share EPT
Date: Thu, 24 Jul 2014 09:23:29 +0800 [thread overview]
Message-ID: <53D06011.5080106@intel.com> (raw)
In-Reply-To: <53CFF40A020000780002539F@mail.emea.novell.com>
On 2014/7/23 23:42, Jan Beulich wrote:
>>>> On 23.07.14 at 11:35, <tiejun.chen@intel.com> wrote:
>> intel_iommu_map_page() does nothing if VT-d shares EPT page table.
>> So rmrr_identity_mapping() never create RMRR mapping but in some
>> cases like some GFX drivers it still need to access RMRR.
>>
>> Here we will create those RMRR mappings even in shared EPT case.
>
> Technically this is fine, but there are mechanical issues:
>
>> @@ -1867,7 +1869,19 @@ static int rmrr_identity_mapping(struct domain *d,
>>
>> while ( base_pfn < end_pfn )
>> {
>> - if ( intel_iommu_map_page(d, base_pfn, base_pfn,
>> + if ( iommu_use_hap_pt(d) ) {
>> + dprintk(XENLOG_DEBUG VTDPREFIX,
>> + "Set RMRR mapping: pfn:0x%lx mfn:0x%lx.\n",
>> + base_pfn, mfn_x(_mfn(base_pfn)));
>
> Do we really need this message, even more so not at guest level?
Its useful to debug as I think, but if you insist on this point, I'm
fine to remove this as well.
> And if you're convinced we need it, please use %#lx instead of
> 0x%lx.
Okay.
>
>> + p2m_lock(p2m);
>> + if ( p2m_set_entry(p2m, base_pfn, _mfn(base_pfn), PAGE_ORDER_4K,
>> + p2m_mmio_direct, p2m_access_rw) ) {
>> + p2m_unlock(p2m);
>> + return -1;
>> + }
>> + p2m_unlock(p2m);
>> + }
>> + else if ( intel_iommu_map_page(d, base_pfn, base_pfn,
>> IOMMUF_readable|IOMMUF_writable) )
>> return -1;
>> base_pfn++;
>
> Apart from the above there are several coding style issues here.
Are you saying this thing?
if ()
{
}
So what about this?
@@ -1867,7 +1869,21 @@ static int rmrr_identity_mapping(struct domain *d,
while ( base_pfn < end_pfn )
{
- if ( intel_iommu_map_page(d, base_pfn, base_pfn,
+ if ( iommu_use_hap_pt(d) )
+ {
+ dprintk(XENLOG_DEBUG VTDPREFIX,
+ "Set RMRR mapping: pfn:%#lx mfn:%#lx.\n",
+ base_pfn, mfn_x(_mfn(base_pfn)));
+ p2m_lock(p2m);
+ if ( p2m_set_entry(p2m, base_pfn, _mfn(base_pfn),
PAGE_ORDER_4K,
+ p2m_mmio_direct, p2m_access_rw) )
+ {
+ p2m_unlock(p2m);
+ return -1;
+ }
+ p2m_unlock(p2m);
+ }
+ else if ( intel_iommu_map_page(d, base_pfn, base_pfn,
IOMMUF_readable|IOMMUF_writable) )
return -1;
base_pfn++;
Thanks
Tiejun
next prev parent reply other threads:[~2014-07-24 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 9:35 [PATCH 1/1] xen:vtd: missing RMRR mapping while share EPT Tiejun Chen
2014-07-23 15:42 ` Jan Beulich
2014-07-24 1:23 ` Chen, Tiejun [this message]
2014-07-24 6:14 ` Jan Beulich
2014-07-24 7:00 ` Chen, Tiejun
2014-07-24 7:15 ` Chen, Tiejun
2014-07-24 7:47 ` Jan Beulich
2014-07-24 7:45 ` Jan Beulich
2014-07-24 8:28 ` Chen, Tiejun
2014-07-24 9:41 ` Jan Beulich
2014-07-24 9:56 ` Chen, Tiejun
2014-07-24 10:11 ` Jan Beulich
2014-07-24 10:42 ` Chen, Tiejun
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=53D06011.5080106@intel.com \
--to=tiejun.chen@intel.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@intel.com \
--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).