From: David Woodhouse <dwmw2@infradead.org>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Ohad Ben-Cohen <ohad@wizery.com>,
David Brown <davidb@codeaurora.org>,
kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 0/2] Introduce iommu_commit() function
Date: Thu, 23 Jun 2011 16:38:54 +0100 [thread overview]
Message-ID: <1308843536.16742.48.camel@i7.infradead.org> (raw)
In-Reply-To: <1308843083-10442-1-git-send-email-joerg.roedel@amd.com>
On Thu, 2011-06-23 at 17:31 +0200, Joerg Roedel wrote:
> David, I think especially VT-d can benefit from such a callback. I will
> implement support for it in the AMD IOMMU driver and post a patch-set
> soon.
>
> Any comments, thoughts?
Ick. We *already* do the flushes as appropriate while we're filling the
page tables. So every time we move on from one page table page to the
next, we'll flush the old one. And when we've *done* filling the page
tables for the range we've been asked to map, we flush the last writes
too.
The problem with KVM is that it calls us over and over again to map a
single 4KiB page.
It doesn't seem simple to make use of a 'commit' function, because we'd
have to keep track of *which* page tables are dirty.
I'd much rather KVM just gave us a list of the pages to map, in a single
call. Or even a 'translation' callback we could call to get the physical
address for each page in the range.
--
dwmw2
next prev parent reply other threads:[~2011-06-23 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 15:31 Joerg Roedel
2011-06-23 15:31 ` [PATCH 1/2] iommu-api: Introduce iommu_comit function Joerg Roedel
2011-06-23 15:31 ` [PATCH 2/2] KVM: IOMMU: Use iommu_commit() in device-passthrough code Joerg Roedel
2011-06-23 15:38 ` David Woodhouse [this message]
2011-06-23 16:21 ` [PATCH 0/2] Introduce iommu_commit() function Roedel, Joerg
2011-06-23 17:20 ` Chris Wright
2011-06-24 8:08 ` Roedel, Joerg
2011-11-16 9:40 ` Avi Kivity
2011-06-29 5:02 ` KyongHo Cho
2011-06-29 5:51 ` Joerg Roedel
2011-11-16 2:00 ` KyongHo Cho
2011-11-16 12:58 ` Joerg Roedel
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=1308843536.16742.48.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=davidb@codeaurora.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.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
all inboxes | Powered by JetHome®