From: "Cédric Le Goater" <clg@redhat.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Avihai Horon" <avihaih@nvidia.com>,
"Joao Martins" <joao.m.martins@oracle.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/2] vfio/migration: Add save_{iterate,complete_precopy}_start trace events
Date: Tue, 5 Nov 2024 08:55:57 +0100 [thread overview]
Message-ID: <9de8ac6e-588b-4789-a8f0-02bfc29d92c9@redhat.com> (raw)
In-Reply-To: <31afb6bed49e8f59d38441135c92cf73bc7d7308.1730750959.git.maciej.szmigiero@oracle.com>
On 11/4/24 22:29, Maciej S. Szmigiero wrote:
> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>
> This way both the start and end points of migrating a particular VFIO
> device are known.
>
> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
> ---
> hw/vfio/migration.c | 9 +++++++++
> hw/vfio/trace-events | 2 ++
> include/hw/vfio/vfio-common.h | 2 ++
> 3 files changed, 13 insertions(+)
>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
next prev parent reply other threads:[~2024-11-05 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 21:29 [PATCH v3 0/2] vfio/migration: new trace events for 9.2 Maciej S. Szmigiero
2024-11-04 21:29 ` [PATCH v3 1/2] vfio/migration: Add save_{iterate, complete_precopy}_start trace events Maciej S. Szmigiero
2024-11-05 7:55 ` Cédric Le Goater [this message]
2024-11-04 21:29 ` [PATCH v3 2/2] vfio/migration: Add vfio_save_block_precopy_empty_hit trace event Maciej S. Szmigiero
2024-11-05 7:56 ` Cédric Le Goater
2024-11-05 12:20 ` Maciej S. Szmigiero
2024-11-05 12:51 ` Cédric Le Goater
2024-11-05 15:20 ` Peter Xu
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=9de8ac6e-588b-4789-a8f0-02bfc29d92c9@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=avihaih@nvidia.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=joao.m.martins@oracle.com \
--cc=mail@maciej.szmigiero.name \
--cc=peterx@redhat.com \
--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).