From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org
Subject: Re: [v3][PATCH 1/1] xen:vtd: missing RMRR mapping while share EPT
Date: Fri, 25 Jul 2014 16:45:31 +0800 [thread overview]
Message-ID: <53D2192B.2010804@intel.com> (raw)
In-Reply-To: <53D22C700200007800025DAC@mail.emea.novell.com>
On 2014/7/25 16:07, Jan Beulich wrote:
>>>> On 25.07.14 at 08:47, <tiejun.chen@intel.com> wrote:
>>> So I think it would be prudent to at least try to detect a clash here
>>> and return an error.
>>
>> Could we check if this pte already present like this?
>>
>> @@ -1870,6 +1872,16 @@ static int rmrr_identity_mapping(struct domain *d,
>> if ( iommu_use_hap_pt(d) )
>> {
>> ASSERT(!iommu_passthrough || !is_hardware_domain(d));
>> + /* get last level pte */
>> + pg_maddr = addr_to_dma_page_maddr(d, ((paddr_t)gfn << PAGE_SHIFT_4K), 0);
>> + page = (struct dma_pte *)map_vtd_domain_page(pg_maddr);
>> + pte = page + address_level_offset(addr, 1);
>> + if ( dma_pte_present(*pte) )
>> + {
>> + printk(XENLOG_ERR VTDPREFIX
>> + "Overlapping RMRRs at %"PRIx64".\n", (paddr_t)base_gfn);
>> + return -1;
>> + }
>> if ( set_mmio_p2m_entry(d, base_pfn, _mfn(base_pfn)) )
>> return -1;
>> }
>
> I think you'd be better off using P2M functions here, even more so
> considering that you're in an iommu_use_hap_pt() guarded code
> section.
Are you pointing p2m->get_entry?
Thanks
Tiejun
next prev parent reply other threads:[~2014-07-25 8:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 11:00 [v3][PATCH 1/1] xen:vtd: missing RMRR mapping while share EPT Tiejun Chen
2014-07-24 11:11 ` Tim Deegan
2014-07-24 11:25 ` Chen, Tiejun
2014-07-24 11:35 ` Tim Deegan
2014-07-24 11:51 ` Chen, Tiejun
2014-07-24 12:16 ` Jan Beulich
2014-07-25 6:48 ` Chen, Tiejun
2014-07-25 7:07 ` Jan Beulich
2014-07-25 7:53 ` Chen, Tiejun
2014-07-25 8:02 ` Jan Beulich
2014-07-25 12:22 ` Tim Deegan
2014-07-24 12:10 ` Jan Beulich
2014-07-25 0:56 ` Zhang, Yang Z
2014-07-25 6:58 ` Jan Beulich
2014-07-25 8:19 ` Zhang, Yang Z
2014-07-25 8:34 ` Jan Beulich
2014-07-25 6:47 ` Chen, Tiejun
2014-07-25 8:07 ` Jan Beulich
2014-07-25 8:45 ` Chen, Tiejun [this message]
2014-07-25 9:14 ` Jan Beulich
2014-07-24 17:12 ` Tian, Kevin
2014-07-25 8:15 ` Jan Beulich
2014-07-25 8:24 ` Zhang, Yang Z
2014-07-25 8:26 ` Chen, Tiejun
2014-07-25 8:28 ` Zhang, Yang Z
2014-07-25 8:30 ` Chen, Tiejun
2014-07-25 8:36 ` Jan Beulich
2014-07-25 8:43 ` Chen, Tiejun
2014-07-25 12:53 ` Tian, Kevin
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=53D2192B.2010804@intel.com \
--to=tiejun.chen@intel.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@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).