From: Joerg Roedel <joro@8bytes.org>
To: KyongHo Cho <pullip.cho@samsung.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, Avi Kivity <avi@redhat.com>,
David Brown <davidb@codeaurora.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/2] Introduce iommu_commit() function
Date: Wed, 29 Jun 2011 07:51:02 +0200 [thread overview]
Message-ID: <20110629055102.GG29299@8bytes.org> (raw)
In-Reply-To: <BANLkTi=mfMfVVOmoZd49fqFnY_kq0hxzDw@mail.gmail.com>
On Wed, Jun 29, 2011 at 02:02:02PM +0900, KyongHo Cho wrote:
> Hi.
>
> On Fri, Jun 24, 2011 at 12:31 AM, Joerg Roedel <joerg.roedel@amd.com> wrote:
> > It needs to be called whenever a some code changed a domain (either by
> > attaching/detaching devices or by mapping/unmapping pages in
> > the domain).
>
> Do you mean we can invalidate IOTLB with this iommu_commit()?
> We need to invalidate IOTLB without updating page table for some
> optimized solutions.
>
> If a device in one domain is moved to other domain, IOTLB of the
> device must be invalidated
> because it contains translation information of the previous domain.
The classic use-case is to do a single iommu-tlb flush after a set of
page-table updates, but flushing iotlbs after moving devices is a
potential use-case too, so the answer is yes.
Regards,
Joerg
next prev parent reply other threads:[~2011-06-29 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 15:31 [PATCH 0/2] Introduce iommu_commit() function 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 ` [PATCH 0/2] Introduce iommu_commit() function David Woodhouse
2011-06-23 16:21 ` 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 [this message]
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=20110629055102.GG29299@8bytes.org \
--to=joro@8bytes.org \
--cc=avi@redhat.com \
--cc=davidb@codeaurora.org \
--cc=dwmw2@infradead.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 \
--cc=pullip.cho@samsung.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 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.