From: Cornelia Huck <cohuck@redhat.com>
To: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com,
pasic@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
alex.williamson@redhat.com, marcel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] s390x/pci: fixup global refresh
Date: Wed, 31 Jan 2018 12:35:33 +0100 [thread overview]
Message-ID: <20180131123533.52c47971.cohuck@redhat.com> (raw)
In-Reply-To: <20180130094715.11578-3-zyimin@linux.vnet.ibm.com>
On Tue, 30 Jan 2018 10:47:14 +0100
Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
> The VFIO common code doesn't provide the possibility to modify a
> previous mapping entry in another way than unmapping and mapping again
> with new properties.
I'm wondering why other architectures don't need that. Is this
refreshing an unique ability on s390 (due to that instruction)?
>
> To avoid -EEXIST DMA mapping error, this we introduce a GHashTable to
s/this//
> store S390IOTLBEntry instances in order to cache the mapped entries.
> When intercepting rpcit instruction, ignore the identical mapped
> entries to avoid doing map operations multiple times and do unmap and
> re-map operations for the case of updating the valid entries. To
> achieve that goal, we also export the DMA walking function and
> optimize the code handling errors in rpcit handler.
How often does such a thing happen in practice?
>
> Acked-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
> Signed-off-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 28 +++++++++-----
> hw/s390x/s390-pci-bus.h | 3 ++
> hw/s390x/s390-pci-inst.c | 95 ++++++++++++++++++++++++++++++++++--------------
> 3 files changed, 90 insertions(+), 36 deletions(-)
Can't really review the rest due to -ENODOC, sorry.
next prev parent reply other threads:[~2018-01-31 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 9:47 [Qemu-devel] [PATCH 0/3] s390x/pci: fixup and optimize IOTLB code Yi Min Zhao
2018-01-30 9:47 ` [Qemu-devel] [PATCH 1/3] s390x/pci: fixup the code walking IOMMU tables Yi Min Zhao
2018-01-31 7:42 ` Thomas Huth
2018-01-31 8:46 ` Yi Min Zhao
2018-01-31 10:58 ` Cornelia Huck
2018-02-01 11:28 ` Yi Min Zhao
2018-02-01 11:56 ` Pierre Morel
2018-02-01 12:15 ` Cornelia Huck
2018-02-01 13:17 ` Pierre Morel
2018-01-30 9:47 ` [Qemu-devel] [PATCH 2/3] s390x/pci: fixup global refresh Yi Min Zhao
2018-01-31 11:35 ` Cornelia Huck [this message]
2018-02-01 12:55 ` Pierre Morel
2018-01-30 9:47 ` [Qemu-devel] [PATCH 3/3] s390x/pci: use the right pal and pba in reg_ioat() Yi Min Zhao
2018-01-31 11:44 ` Cornelia Huck
2018-02-01 11:33 ` Pierre Morel
2018-02-01 12:02 ` Cornelia Huck
2018-02-02 3:50 ` Yi Min Zhao
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=20180131123533.52c47971.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=marcel@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zyimin@linux.vnet.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).