From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] memory: Fix IOMMU replay base address
Date: Mon, 22 Feb 2016 23:12:27 +1100 [thread overview]
Message-ID: <20160222121227.GN2808@voom.fritz.box> (raw)
In-Reply-To: <56CAF2B3.2030502@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
On Mon, Feb 22, 2016 at 10:36:19PM +1100, Alexey Kardashevskiy wrote:
> On 02/22/2016 05:26 PM, David Gibson wrote:
> >On Mon, Feb 22, 2016 at 05:09:39PM +1100, Alexey Kardashevskiy wrote:
> >>Since a788f227 "memory: Allow replay of IOMMU mapping notifications"
> >>when new VFIO listener is added, all existing IOMMU mappings are replayed.
> >>However there is a problem that the base address of an IOMMU memory region
> >>(IOMMU MR) is ignored which is not a problem for the existing user (which is
> >>pseries) with its default 32bit DMA window starting at 0 but it is if there is
> >>another DMA window.
> >>
> >>This adjusts the replaying address by mr->addr.
> >
> >Uh.. this doesn't look right to me. AFAICT from the existing
> >implementations the 'addr' parameter to the translate function is an
> >offset within the memory region, which would make the original version
> >correct.
>
> Ok, then spapr_tce_translate_iommu() needs to be fixed. Or I am missing
> something here? The @addr field is definitely ignored now.
I think at least one of us is missing something. In the normal AS
translation path, IIUC, it will subtract the mr->addr value to give
offsets which are passed to translate. It uses those offsets to find
the TCE and returns a translated address. Where else the @addr be
used?
>
>
> >
> >>Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> >>---
> >> memory.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >>diff --git a/memory.c b/memory.c
> >>index 09041ed..377269b 100644
> >>--- a/memory.c
> >>+++ b/memory.c
> >>@@ -1436,7 +1436,7 @@ void memory_region_iommu_replay(MemoryRegion *mr, Notifier *n,
> >> IOMMUTLBEntry iotlb;
> >>
> >> for (addr = 0; addr < memory_region_size(mr); addr += granularity) {
> >>- iotlb = mr->iommu_ops->translate(mr, addr, is_write);
> >>+ iotlb = mr->iommu_ops->translate(mr, mr->addr + addr, is_write);
> >> if (iotlb.perm != IOMMU_NONE) {
> >> n->notify(n, &iotlb);
> >> }
> >
>
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-22 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 6:09 [Qemu-devel] [PATCH qemu] memory: Fix IOMMU replay base address Alexey Kardashevskiy
2016-02-22 6:26 ` David Gibson
2016-02-22 11:36 ` Alexey Kardashevskiy
2016-02-22 12:12 ` David Gibson [this message]
2016-02-23 2:11 ` Alexey Kardashevskiy
2016-02-23 6:20 ` David Gibson
2016-02-23 9:00 ` Alexey Kardashevskiy
2016-02-23 9:56 ` Paolo Bonzini
2016-02-23 11:25 ` David Gibson
2016-02-24 0:19 ` Alexey Kardashevskiy
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=20160222121227.GN2808@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--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).