From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: "junqing@pku.edu.cn" <junqing@pku.edu.cn>,
CHENG Yueqiang <yqcheng.2008@phdis.smu.edu.sg>,
"zhangzhi2022@hotmail.com" <zhangzhi2022@hotmail.com>,
xiantao.zhang@intel.com
Subject: Re: [PATCH] VT-d: fix TLB flushing in dma_pte_clear_one()
Date: Mon, 18 Nov 2013 03:58:25 -0800 [thread overview]
Message-ID: <CEAF40E1.65967%keir.xen@gmail.com> (raw)
In-Reply-To: <528A06C90200007800103FA4@nat28.tlf.novell.com>
On 18/11/2013 03:23, "Jan Beulich" <JBeulich@suse.com> wrote:
> The third parameter of __intel_iommu_iotlb_flush() is to indicate
> whether the to be flushed entry was a present one. A few lines before,
> we bailed if !dma_pte_present(*pte), so there's no need to check the
> flag here again - we can simply always pass TRUE here.
>
> This is XSA-78.
>
> Suggested-by: Cheng Yueqiang <yqcheng.2008@phdis.smu.edu.sg>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- a/xen/drivers/passthrough/vtd/iommu.c
> +++ b/xen/drivers/passthrough/vtd/iommu.c
> @@ -646,7 +646,7 @@ static void dma_pte_clear_one(struct dom
> iommu_flush_cache_entry(pte, sizeof(struct dma_pte));
>
> if ( !this_cpu(iommu_dont_flush_iotlb) )
> - __intel_iommu_iotlb_flush(domain, addr >> PAGE_SHIFT_4K , 0, 1);
> + __intel_iommu_iotlb_flush(domain, addr >> PAGE_SHIFT_4K, 1, 1);
>
> unmap_vtd_domain_page(page);
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-11-18 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 14:33 [BUG] IOTLB is not flushed in IOMMU Unmap Process CHENG Yueqiang
2013-11-18 11:22 ` Jan Beulich
2013-11-18 11:23 ` [PATCH] VT-d: fix TLB flushing in dma_pte_clear_one() Jan Beulich
2013-11-18 11:43 ` Andrew Cooper
2013-11-18 11:58 ` Keir Fraser [this message]
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=CEAF40E1.65967%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=junqing@pku.edu.cn \
--cc=xen-devel@lists.xenproject.org \
--cc=xiantao.zhang@intel.com \
--cc=yqcheng.2008@phdis.smu.edu.sg \
--cc=zhangzhi2022@hotmail.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).