From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: walling@linux.ibm.com, borntraeger@de.ibm.com, rth@twiddle.net,
david@redhat.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
pasic@linux.ibm.com, thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH] s390x/pci: Set the iommu region size as guest wants
Date: Wed, 9 Jan 2019 13:59:19 +0100 [thread overview]
Message-ID: <20190109135919.3ebb7d03.cohuck@redhat.com> (raw)
In-Reply-To: <1546968819-8166-1-git-send-email-pmorel@linux.ibm.com>
On Tue, 8 Jan 2019 18:33:39 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> The size of the accessible iommu memory region in the guest
> is calculated by the gues as:
s/gues/guest/
> (PCI Address Limit) - (PCI Base Address) + 1.
>
> Let's use this value to limit the IOMMU region size.
These are values provided by the guest in the mpcifc call, aren't they?
Let's mention that in the patch description, so it is more obvious :)
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index 69e0671..e97696a 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -660,7 +660,7 @@ void s390_pci_iommu_enable(S390PCIIOMMU *iommu)
> char *name = g_strdup_printf("iommu-s390-%04x", iommu->pbdev->uid);
> memory_region_init_iommu(&iommu->iommu_mr, sizeof(iommu->iommu_mr),
> TYPE_S390_IOMMU_MEMORY_REGION, OBJECT(&iommu->mr),
> - name, iommu->pal + 1);
> + name, iommu->pal - iommu->pba + 1);
> iommu->enabled = true;
> memory_region_add_subregion(&iommu->mr, 0, MEMORY_REGION(&iommu->iommu_mr));
> g_free(name);
next prev parent reply other threads:[~2019-01-09 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 17:33 [Qemu-devel] [PATCH] s390x/pci: Set the iommu region size as guest wants Pierre Morel
2019-01-09 12:59 ` Cornelia Huck [this message]
2019-01-10 12:50 ` Pierre Morel
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=20190109135919.3ebb7d03.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).