From: "Cédric Le Goater" <clg@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Joao Martins" <joao.m.martins@oracle.com>,
qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
Avihai Horon <avihaih@nvidia.com>
Subject: Re: [PATCH v4 0/2] hw/vfio: Improve vfio_get_dirty_bitmap() tracepoint
Date: Tue, 13 Jun 2023 11:37:33 +0200 [thread overview]
Message-ID: <79b5565b-1d44-f6e5-6c55-66ff403353b6@redhat.com> (raw)
In-Reply-To: <a043b593-c576-5dd2-8ac7-63ecad5533af@linaro.org>
On 6/13/23 11:34, Philippe Mathieu-Daudé wrote:
> On 30/5/23 20:05, Joao Martins wrote:
>
>> Joao Martins (2):
>> exec/ram_addr: return number of dirty pages in
>> cpu_physical_memory_set_dirty_lebitmap()
>> hw/vfio: Add number of dirty pages to vfio_get_dirty_bitmap tracepoint
>
> Queued, thanks.
>
I had taken it into my vfio-next branch. As you wish.
Thanks,
C.
next prev parent reply other threads:[~2023-06-13 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 18:05 [PATCH v4 0/2] hw/vfio: Improve vfio_get_dirty_bitmap() tracepoint Joao Martins
2023-05-30 18:05 ` [PATCH v4 1/2] exec/ram_addr: return number of dirty pages in cpu_physical_memory_set_dirty_lebitmap() Joao Martins
2023-05-30 18:05 ` [PATCH v4 2/2] hw/vfio: Add number of dirty pages to vfio_get_dirty_bitmap tracepoint Joao Martins
2023-06-05 22:58 ` Alex Williamson
2023-06-13 9:34 ` [PATCH v4 0/2] hw/vfio: Improve vfio_get_dirty_bitmap() tracepoint Philippe Mathieu-Daudé
2023-06-13 9:37 ` Cédric Le Goater [this message]
2023-06-13 9:45 ` Philippe Mathieu-Daudé
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=79b5565b-1d44-f6e5-6c55-66ff403353b6@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=david@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).