From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
Lan Tianyu <tianyu.lan@intel.com>,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S.Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 7/7] intel_iommu: support passthrough (PT)
Date: Thu, 20 Apr 2017 13:28:26 +0800 [thread overview]
Message-ID: <20170420052826.GC26087@pxdev.xzpeter.org> (raw)
In-Reply-To: <a9ec14d0-3c43-a66a-afdb-13f644857004@redhat.com>
On Thu, Apr 20, 2017 at 01:18:28PM +0800, Jason Wang wrote:
>
>
> On 2017年04月18日 12:21, Peter Xu wrote:
> >On Tue, Apr 18, 2017 at 12:00:13PM +0800, Jason Wang wrote:
> >>
> >>On 2017年04月18日 11:50, Peter Xu wrote:
> >>>On Tue, Apr 18, 2017 at 11:23:35AM +0800, Jason Wang wrote:
> >>>>On 2017年04月17日 18:58, Peter Xu wrote:
> >>>[...]
> >>>
> >>>>>+static void vtd_switch_address_space(VTDAddressSpace *as)
> >>>>>+{
> >>>>>+ bool use_iommu;
> >>>>>+
> >>>>>+ assert(as);
> >>>>>+
> >>>>>+ use_iommu = as->iommu_state->dmar_enabled;
> >>>>>+ if (use_iommu) {
> >>>>>+ /* Further checks per-device configuration */
> >>>>>+ use_iommu &= !vtd_dev_pt_enabled(as);
> >>>>>+ }
> >>>>Looks like you can use as->iommu_state->dmar_enabled &&
> >>>>!vtd_dev_pt_enabled(as)
> >>>vtd_dev_pt_enalbed() needs to read the guest memory (starting from
> >>>reading root entry), which is slightly slow. I was trying to avoid
> >>>unecessary reads.
> >>>
> >>>[...]
> >>I think compiler won't go to vtd_dev_pt_enabled() if dmar_enabled is false.
> >You are right. I'll switch.
> >
> >>>>>@@ -991,6 +1058,18 @@ static void vtd_do_iommu_translate(VTDAddressSpace *vtd_as, PCIBus *bus,
> >>>>> cc_entry->context_cache_gen = s->context_cache_gen;
> >>>>> }
> >>>>>+ /*
> >>>>>+ * We don't need to translate for pass-through context entries.
> >>>>>+ * Also, let's ignore IOTLB caching as well for PT devices.
> >>>>>+ */
> >>>>>+ if (vtd_ce_get_type(&ce) == VTD_CONTEXT_TT_PASS_THROUGH) {
> >>>>>+ entry->translated_addr = entry->iova;
> >>>>>+ entry->addr_mask = VTD_PAGE_SIZE - 1;
> >>>>>+ entry->perm = IOMMU_RW;
> >>>>>+ trace_vtd_translate_pt(source_id, entry->iova);
> >>>>>+ return;
> >>>>>+ }
> >>>>Several questions here:
> >>>>
> >>>>1) Is this just for vhost?
> >>>No. When caching mode is not enabled, all passthroughed devices should
> >>>be using this path.
> >>Ok, then it looks better to switch the address space if we've found it was
> >>PT?
> >Do you mean to switch in that if() above? Then when invalidate context
> >entry, we switch back if needed?
>
> Yes.
Sure. Do you mind if I put this into another standalone patch? I see
it an enhancement that can be separated from current one. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2017-04-20 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1492426712-12230-1-git-send-email-peterx@redhat.com>
[not found] ` <1492426712-12230-8-git-send-email-peterx@redhat.com>
2017-04-18 3:23 ` [Qemu-devel] [PATCH 7/7] intel_iommu: support passthrough (PT) Jason Wang
2017-04-18 3:50 ` Peter Xu
2017-04-18 4:00 ` Jason Wang
2017-04-18 4:21 ` Peter Xu
2017-04-20 5:18 ` Jason Wang
2017-04-20 5:28 ` Peter Xu [this message]
2017-04-20 6:05 ` Jason Wang
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=20170420052826.GC26087@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jasowang@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tianyu.lan@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).