From: Eric Farman <farman@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>, qemu-s390x@nongnu.org
Cc: thuth@redhat.com, clg@redhat.com, pasic@linux.ibm.com,
borntraeger@linux.ibm.com, richard.henderson@linaro.org,
david@redhat.com, iii@linux.ibm.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] s390x/pci: small set of fixes
Date: Mon, 13 Nov 2023 09:49:18 -0500 [thread overview]
Message-ID: <58917bcc486fcbaa5c295f218ab7e049e05d05e6.camel@linux.ibm.com> (raw)
In-Reply-To: <20231110175108.465851-1-mjrosato@linux.ibm.com>
On Fri, 2023-11-10 at 12:51 -0500, Matthew Rosato wrote:
> The following set of changes are associated with issues exposed by
> testing
> of the 'vfio: Adopt iommufd' series.
...snip...
> Matthew Rosato (2):
> s390x/pci: bypass vfio DMA counting when using cdev
> s390x/pci: only limit DMA aperture if vfio DMA limit reported
>
> hw/s390x/s390-pci-vfio.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
Apologies for missing v1 while I was out, but FWIW, for the series:
Reviewed-by: Eric Farman <farman@linux.ibm.com>
prev parent reply other threads:[~2023-11-13 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:51 [PATCH v2 0/2] s390x/pci: small set of fixes Matthew Rosato
2023-11-10 17:51 ` [PATCH v2 1/2] s390x/pci: bypass vfio DMA counting when using cdev Matthew Rosato
2023-11-10 17:51 ` [PATCH v2 2/2] s390x/pci: only limit DMA aperture if vfio DMA limit reported Matthew Rosato
2023-11-13 21:24 ` Michael Tokarev
2023-11-13 21:49 ` Matthew Rosato
2023-11-13 6:29 ` [PATCH v2 0/2] s390x/pci: small set of fixes Thomas Huth
2023-11-13 14:49 ` Eric Farman [this message]
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=58917bcc486fcbaa5c295f218ab7e049e05d05e6.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).