From: Peter Xu <peterx@redhat.com>
To: "Aviv B.D." <bd.aviv@gmail.com>
Cc: marcel@redhat.com, Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH][RFC] IOMMU: Add Support to VFIO devices with vIOMMU present
Date: Mon, 21 Mar 2016 10:30:12 +0800 [thread overview]
Message-ID: <20160321023012.GA4468@pxdev.xzpeter.org> (raw)
In-Reply-To: <CAM3WwMiW107ETixPdc+SJ=T4xsn-1zBsUfnKt0zbvDzx_iJuaA@mail.gmail.com>
On Sat, Mar 19, 2016 at 11:40:04AM +0200, Aviv B.D. wrote:
[...]
> As far as I understand the code, currently there is no way to turn off the
> IOTLB.
> Furthermore. the IOTLB is not implemented as LRU, and actually caches
> (indefinitely)
> any accessed address, without any size constrains. I use those assumptions
> to know
> whether the current invalidation is for unmap operation or map operation.
Please have a look at VTD_IOTLB_MAX_SIZE. It seems to be the size of
the hash.
Btw, I guess it's a much bigger problem if IOTLB has unlimited cache
size...
Thanks.
-- peterx
next prev parent reply other threads:[~2016-03-21 2:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 16:13 [Qemu-devel] [PATCH][RFC] IOMMU: Add Support to VFIO devices with vIOMMU present Aviv B.D.
2016-03-14 18:52 ` Marcel Apfelbaum
2016-03-14 18:58 ` Jan Kiszka
2016-03-15 7:00 ` Michael S. Tsirkin
2016-03-15 8:52 ` Peter Xu
2016-03-17 11:17 ` Aviv B.D.
2016-03-18 3:06 ` Peter Xu
2016-03-19 9:40 ` Aviv B.D.
2016-03-21 2:30 ` Peter Xu [this message]
2016-03-22 8:13 ` Aviv B.D.
2016-03-15 10:53 ` Michael S. Tsirkin
2016-03-17 11:58 ` Aviv B.D.
2016-03-23 14:34 ` Michael S. Tsirkin
2016-03-23 14:33 ` Michael S. Tsirkin
2016-03-26 14:47 ` Aviv B.D.
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=20160321023012.GA4468@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bd.aviv@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=marcel@redhat.com \
--cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.