From: Alex Williamson <alex.williamson@redhat.com>
To: Kunkun Jiang <jiangkunkun@huawei.com>
Cc: "open list:All patches CC here" <qemu-devel@nongnu.org>,
Eric Auger <eric.auger@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
tangnianyao@huawei.com, ganqixin@huawei.com,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH v2 0/2] vfio: Some fixes about vfio-pci MMIO RAM mapping
Date: Fri, 8 Oct 2021 09:05:45 -0600 [thread overview]
Message-ID: <20211008090546.2b8e10cb.alex.williamson@redhat.com> (raw)
In-Reply-To: <59ccc25e-3a5e-8963-209e-a3c9e5dece92@huawei.com>
On Fri, 8 Oct 2021 09:27:04 +0800
Kunkun Jiang <jiangkunkun@huawei.com> wrote:
> Kindly ping,
>
> Hi all,
>
> Will this patch be picked up soon, or is there any other advice?
More reviews are always appreciated. Requesting reviews by your
colleagues and/or exchanging reviews with other contributors are good
ways to offload maintainers and provide more confidence in the patch
series. Thanks,
Alex
> On 2021/9/14 9:53, Kunkun Jiang wrote:
> > This series include patches as below:
> >
> > Patch 1:
> > - vfio/pci: Fix vfio-pci sub-page MMIO BAR mmaping in live migration
> >
> > Patch 2:
> > - Added a trace point to informe users when a MMIO RAM ection less than PAGE_SIZE
> >
> > History:
> >
> > v1 -> v2:
> > - Add iterate sub-page BARs in vfio_pci_load_config and try to update them [Alex Williamson]
> >
> > Kunkun Jiang (2):
> > vfio/pci: Fix vfio-pci sub-page MMIO BAR mmaping in live migration
> > vfio/common: Add trace point when a MMIO RAM section less than
> > PAGE_SIZE
> >
> > hw/vfio/common.c | 7 +++++++
> > hw/vfio/pci.c | 15 ++++++++++++++-
> > 2 files changed, 21 insertions(+), 1 deletion(-)
> >
>
prev parent reply other threads:[~2021-10-08 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 1:53 [PATCH v2 0/2] vfio: Some fixes about vfio-pci MMIO RAM mapping Kunkun Jiang
2021-09-14 1:53 ` [PATCH v2 1/2] vfio/pci: Fix vfio-pci sub-page MMIO BAR mmaping in live migration Kunkun Jiang
2021-10-21 16:15 ` Eric Auger
2021-10-22 10:01 ` Kunkun Jiang
2021-10-23 14:26 ` Eric Auger
2021-10-24 2:09 ` Kunkun Jiang
2021-09-14 1:53 ` [PATCH v2 2/2] vfio/common: Add trace point when a MMIO RAM section less than PAGE_SIZE Kunkun Jiang
2021-10-21 17:02 ` Eric Auger
2021-10-22 10:02 ` Kunkun Jiang
2021-10-08 1:27 ` [PATCH v2 0/2] vfio: Some fixes about vfio-pci MMIO RAM mapping Kunkun Jiang
2021-10-08 15:05 ` Alex Williamson [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=20211008090546.2b8e10cb.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=ganqixin@huawei.com \
--cc=jiangkunkun@huawei.com \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=tangnianyao@huawei.com \
--cc=wanghaibin.wang@huawei.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).