From: Richard Henderson <richard.henderson@linaro.org>
To: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Cc: Kunkun Jiang <jiangkunkun@huawei.com>,
Nianyao Tang <tangnianyao@huawei.com>,
Qixin Gan <ganqixin@huawei.com>
Subject: Re: [PULL 0/2] VFIO update 2021-11-01 (for v6.2)
Date: Tue, 2 Nov 2021 08:44:17 -0400 [thread overview]
Message-ID: <a0ce88df-b4cf-533b-a59e-c9c155a6fe6d@linaro.org> (raw)
In-Reply-To: <163579674962.3486201.2525541279968158386.stgit@omen>
On 11/1/21 4:01 PM, Alex Williamson wrote:
> The following changes since commit af531756d25541a1b3b3d9a14e72e7fedd941a2e:
>
> Merge remote-tracking branch 'remotes/philmd/tags/renesas-20211030' into staging (2021-10-30 11:31:41 -0700)
>
> are available in the Git repository at:
>
> git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20211101.0
>
> for you to fetch changes up to e4b34708388b20f1ceb55f1d563d8da925a32424:
>
> vfio/common: Add a trace point when a MMIO RAM section cannot be mapped (2021-11-01 12:17:51 -0600)
>
> ----------------------------------------------------------------
> VFIO update 2021-11-01
>
> * Re-enable expanded sub-page BAR mappings after migration (Kunkun Jiang)
>
> * Trace dropped listener sections due to page alignment (Kunkun Jiang)
>
> ----------------------------------------------------------------
> Kunkun Jiang (2):
> vfio/pci: Add support for mmapping sub-page MMIO BARs after live migration
> vfio/common: Add a trace point when a MMIO RAM section cannot be mapped
>
> hw/vfio/common.c | 7 +++++++
> hw/vfio/pci.c | 19 ++++++++++++++++++-
> 2 files changed, 25 insertions(+), 1 deletion(-)
Applied, thanks.
r~
prev parent reply other threads:[~2021-11-02 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 20:01 [PULL 0/2] VFIO update 2021-11-01 (for v6.2) Alex Williamson
2021-11-01 20:01 ` [PULL 1/2] vfio/pci: Add support for mmapping sub-page MMIO BARs after live migration Alex Williamson
2021-11-01 20:01 ` [PULL 2/2] vfio/common: Add a trace point when a MMIO RAM section cannot be mapped Alex Williamson
2021-11-02 12:44 ` Richard Henderson [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=a0ce88df-b4cf-533b-a59e-c9c155a6fe6d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=ganqixin@huawei.com \
--cc=jiangkunkun@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=tangnianyao@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).