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 16:28:03 +0800 [thread overview]
Message-ID: <53D0C393.5080000@intel.com> (raw)
In-Reply-To: <53D0D5BE0200007800025643@mail.emea.novell.com>
On 2014/7/24 15:45, Jan Beulich wrote:
>>>> On 24.07.14 at 09:00, <tiejun.chen@intel.com> wrote:
>> On 2014/7/24 14:14, Jan Beulich wrote:
>>>>>> On 24.07.14 at 03:23, <tiejun.chen@intel.com> wrote:
>>>> @@ -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) )
>>>
>>> Don't you, btw, need to extend this condition by
>>> && (!iommu_passthrough || !is_hardware_domain(d))?
>>
>> Why do we need these checks here?
>
> At least for documentation purposes: It would be wrong to try to
> establish these mappings. I reckon iommu_use_hap_pt() implies the
> combined other condition, so an ASSERT() would presumably be fine
> as well (and get even closer to the intended documentation purpose).
>
I think if() should be reasonable here. Because
intel_iommu_map_page()
{
...
/* do nothing if dom0 and iommu supports pass thru */
if ( iommu_passthrough && is_hardware_domain(d) )
return 0;
We just do nothing to return simply. But if ASSERT will cause abort.
Thanks
Tiejun
next prev parent reply other threads:[~2014-07-24 8:28 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
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 [this message]
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=53D0C393.5080000@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).