iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Christoffer Dall <cdall@linaro.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Jean-Philippe Brucker <Jean-Philippe.Brucker@arm.com>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Peter Xu <peterx@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Andrew Jones <drjones@redhat.com>
Subject: Re: userspace emulated smmu/vfio integration: how to trap updates to the table structures?
Date: Tue, 2 May 2017 10:13:17 +0200	[thread overview]
Message-ID: <04a1dd2e-737c-3cb0-6cd8-71a783f463c8@redhat.com> (raw)
In-Reply-To: <CAMJs5B_LjRzvGrHGGUVtdGurjKPgg7_KOrvYAwmgpYXh2Qab8w@mail.gmail.com>

Hi Christoffer,

On 02/05/2017 09:53, Christoffer Dall wrote:
> On Tue, May 2, 2017 at 9:30 AM, Auger Eric <eric.auger@redhat.com> wrote:
>> Hi Will, Robin, Jean-Philippe,
>>
>> I have been working on the integration between user-space emulated
>> SMMU-v3 and VFIO in QEMU. At the moment I fail identifying a proper easy
>> way to trap page table updates. This is requested to keep the host
>> translation structures consistent to guest translation structures.
>>
>> On Intel VTD there is a so-called "caching mode" (CM, see VTD spec
>> paragraph 6.1) that forces the OS to explicitly invalidate caches
>> whenever it updates any remapping structure (updates to not-present or
>> present entries). Those invalidation commands are used to trap and
>> update host structures. This mode was devised for virtualization. I was
>> not able to find such "caching mode" on ARM SMMU. Is there any?
>>
>> If not, do you have any other suggestion, I mean, besides the
>> virtio-based solution.
>>
>>
> Worst case, can you make the guest page tables read-only and catch the
> faults and propagate changes to SMMU translations?

The issue I foresee is there are up to 4 level of page tables to trap.
This would lead to plenty of regions to "translate" on qemu side. Also,
besides the 1st level pointed by TTBR found in stage 1 context
descriptor, other page regions would be discovered dynamically as
mapping are built. To me this is the last resort solution if confirmed
feasible.

Thanks

Eric


> 
> -Christoffer
> 

  reply	other threads:[~2017-05-02  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  7:30 userspace emulated smmu/vfio integration: how to trap updates to the table structures? Auger Eric
2017-05-02  7:53 ` Christoffer Dall
2017-05-02  8:13   ` Auger Eric [this message]
2017-05-02  8:17     ` Christoffer Dall
2017-05-02 15:22       ` Michael S. Tsirkin
2017-05-02 15:42         ` Robin Murphy
     [not found]           ` <0d310113-af68-2154-8dd3-a00b0c9a76ed-5wv7dgnIgG8@public.gmane.org>
2017-05-02 16:20             ` Michael S. Tsirkin
2017-05-02 17:01             ` Auger Eric
2017-05-02 15:26 ` Michael S. Tsirkin
2017-05-02 17:36 ` Michael S. Tsirkin
2017-05-09 13:48   ` Auger Eric

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=04a1dd2e-737c-3cb0-6cd8-71a783f463c8@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=Jean-Philippe.Brucker@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=alex.williamson@redhat.com \
    --cc=cdall@linaro.org \
    --cc=drjones@redhat.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=robin.murphy@arm.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).