From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
To: Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@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: [PATCH v3 0/2] vfio/migration: new trace events for 9.2
Date: Mon, 4 Nov 2024 22:29:05 +0100 [thread overview]
Message-ID: <cover.1730750959.git.maciej.szmigiero@oracle.com> (raw)
From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
This is essentially the v2 patch from here:
https://lore.kernel.org/qemu-devel/8fbb9cc40d9db570eff0a02e49104835014a5a4d.1730731549.git.maciej.szmigiero@oracle.com/
split into two separate patches, with a few small requested changes, like:
* Rename vfio_precopy_empty_hit into vfio_save_block_precopy_empty_hit,
* Add an 'event_' prefix to the related struct VFIOMigration new members,
* Change trace event '_started' suffix to '_start' for consistency with
other trace events (but keep the variable name as 'started' since it
tracks whether that event has already happened).
Maciej S. Szmigiero (2):
vfio/migration: Add save_{iterate,complete_precopy}_start trace events
vfio/migration: Add vfio_save_block_precopy_empty_hit trace event
hw/vfio/migration.c | 17 +++++++++++++++++
hw/vfio/trace-events | 3 +++
include/hw/vfio/vfio-common.h | 3 +++
3 files changed, 23 insertions(+)
next reply other threads:[~2024-11-04 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 21:29 Maciej S. Szmigiero [this message]
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 ` [PATCH v3 1/2] vfio/migration: Add save_{iterate,complete_precopy}_start " Cédric Le Goater
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=cover.1730750959.git.maciej.szmigiero@oracle.com \
--to=mail@maciej.szmigiero.name \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=avihaih@nvidia.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=joao.m.martins@oracle.com \
--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).