From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Jason Wang <jasowang@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 2/3] exec: simplify address_space_get_iotlb_entry
Date: Tue, 6 Jun 2017 16:34:30 +0200 [thread overview]
Message-ID: <f68502e6-875c-0e46-f7cf-127c23513d20@redhat.com> (raw)
In-Reply-To: <20170605030725.GF4056@pxdev.xzpeter.org>
On 05/06/2017 05:07, Peter Xu wrote:
> I don't sure whether it'll be a good interface for IOTLB. AFAIU at
> least for VT-d, the IOMMU translation is page aligned which is defined
> by spec, so it makes sense that (again at least for VT-d) here we'd
> better just use page_mask/addr_mask.
>
> That's also how I know about IOMMU in general - I assume it do the
> translations always with page masks (never arbitary length), though
> page size can differ from platfrom to platform, that's why here the
> IOTLB interface used addr_mask, then it works for all platforms. I
> don't know whether I'm 100% correct here though.
>
> Maybe David/Paolo/... would comment as well?
I would ask David. There are PowerPC MMUs that allow fast lookup of
arbitrarily-sized windows (not necessarily power of two), so maybe the
IOMMUs can do the same.
Paolo
next prev parent reply other threads:[~2017-06-06 14:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 11:50 [Qemu-devel] [PATCH 0/3] exec: further refine address_space_get_iotlb_entry() Peter Xu
2017-06-02 11:50 ` [Qemu-devel] [PATCH 1/3] exec: add page_mask for address_space_do_translate Peter Xu
2017-06-02 16:45 ` Michael S. Tsirkin
2017-06-05 2:52 ` Peter Xu
2017-06-02 11:50 ` [Qemu-devel] [PATCH 2/3] exec: simplify address_space_get_iotlb_entry Peter Xu
2017-06-02 16:49 ` Michael S. Tsirkin
2017-06-05 3:07 ` Peter Xu
2017-06-06 14:34 ` Paolo Bonzini [this message]
2017-06-06 23:47 ` David Gibson
2017-06-07 3:44 ` Peter Xu
2017-06-07 13:07 ` Michael S. Tsirkin
2017-06-08 6:11 ` Peter Xu
2017-06-08 18:59 ` Michael S. Tsirkin
2017-06-09 1:58 ` Peter Xu
2017-06-09 2:37 ` David Gibson
2017-06-11 10:09 ` Michael S. Tsirkin
2017-06-11 12:10 ` David Gibson
2017-06-12 2:34 ` Peter Xu
2017-06-12 3:07 ` Michael S. Tsirkin
2017-06-12 4:04 ` Peter Xu
2017-06-14 18:34 ` Michael S. Tsirkin
2017-06-15 2:31 ` Peter Xu
2017-06-15 2:57 ` Peter Xu
2017-06-16 15:33 ` Michael S. Tsirkin
2017-06-07 13:01 ` Paolo Bonzini
2017-06-02 11:50 ` [Qemu-devel] [PATCH 3/3] vhost: iommu: cache static mapping if there is Peter Xu
2017-06-02 15:45 ` Michael S. Tsirkin
2017-06-05 3:15 ` Peter Xu
2017-06-05 4:07 ` Jason Wang
2017-06-05 15:05 ` Michael S. Tsirkin
2017-06-02 16:51 ` Michael S. Tsirkin
2017-06-02 14:51 ` [Qemu-devel] [PATCH 0/3] exec: further refine address_space_get_iotlb_entry() Michael S. Tsirkin
2017-06-05 3:20 ` Peter Xu
2017-06-06 15:29 ` Michael S. Tsirkin
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=f68502e6-875c-0e46-f7cf-127c23513d20@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).