From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v3 16/20] vhost_user: Turn vhost-user message reports to trace()
Date: Mon, 3 Feb 2025 14:11:10 +1100 [thread overview]
Message-ID: <Z6AzzufWyCJEkAgM@zatzit> (raw)
In-Reply-To: <20250131193953.3034031-17-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
On Fri, Jan 31, 2025 at 08:39:49PM +0100, Stefano Brivio wrote:
> Having every vhost-user message printed as part of debug output makes
> debugging anything else a bit complicated.
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
I'm a little bit baffled by this. You're changing to trace() a couple
of relatively rare messages, that I think belong in debug() category,
but *not* changing some things that definitely should be trace() -
such as the ones in vu_send_single() and vu_kick_cb().
> ---
> vhost_user.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/vhost_user.c b/vhost_user.c
> index 2dde405..1092387 100644
> --- a/vhost_user.c
> +++ b/vhost_user.c
> @@ -640,8 +640,8 @@ static bool vu_set_vring_num_exec(struct vu_dev *vdev,
> unsigned int idx = msg->payload.state.index;
> unsigned int num = msg->payload.state.num;
>
> - debug("State.index: %u", idx);
> - debug("State.num: %u", num);
> + trace("State.index: %u", idx);
> + trace("State.num: %u", num);
> vdev->vq[idx].vring.num = num;
>
> return false;
> @@ -1176,11 +1176,11 @@ void vu_control_handler(struct vu_dev *vdev, int fd, uint32_t events)
> vu_sock_reset(vdev);
> return;
> }
> - debug("================ Vhost user message ================");
> - debug("Request: %s (%d)", vu_request_to_string(msg.hdr.request),
> + trace("================ Vhost user message ================");
> + trace("Request: %s (%d)", vu_request_to_string(msg.hdr.request),
> msg.hdr.request);
> - debug("Flags: 0x%x", msg.hdr.flags);
> - debug("Size: %u", msg.hdr.size);
> + trace("Flags: 0x%x", msg.hdr.flags);
> + trace("Size: %u", msg.hdr.size);
>
> need_reply = msg.hdr.flags & VHOST_USER_NEED_REPLY_MASK;
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-03 5:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:39 [PATCH v3 00/20] Draft, incomplete series introducing state migration Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 01/20] tcp: Always pass NULL event with EPOLL_CTL_DEL Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 02/20] util: Rename and make global vu_remove_watch() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 03/20] icmp, udp: Pad time_t timestamp to 64-bit to ease state migration Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 04/20] flow, flow_table: Pad flow table entries to 128 bytes, hash entries to 32 bits Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 05/20] flow_table: Use size in extern declaration for flowtab Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 06/20] util: Add read_remainder() and read_all_buf() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 07/20] Introduce facilities for guest migration on top of vhost-user infrastructure Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 08/20] Introduce passt-repair Stefano Brivio
2025-02-03 1:46 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 09/20] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-03 5:22 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 10/20] flow, tcp: Basic pre-migration source handler to dump sequence numbers Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 11/20] migrate: vu_migrate_{source,target}() aren't actually vu speciic Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 12/20] migrate: Move repair_sock_init() to vu_init() Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 13/20] migrate: Make more handling common rather than vhost-user specific Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 14/20] migrate: Don't handle the migration channel through epoll Stefano Brivio
2025-02-03 1:50 ` David Gibson
2025-02-03 5:38 ` Stefano Brivio
2025-02-03 8:45 ` David Gibson
2025-02-03 2:16 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 15/20] flow, flow_table: Export declaration of hash table Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 16/20] vhost_user: Turn vhost-user message reports to trace() Stefano Brivio
2025-02-03 3:11 ` David Gibson [this message]
2025-02-03 6:10 ` Stefano Brivio
2025-02-03 8:47 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 17/20] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-03 1:55 ` David Gibson
2025-02-03 6:09 ` Stefano Brivio
2025-02-03 8:52 ` David Gibson
2025-02-03 9:44 ` Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 18/20] tcp: Get our socket port using getsockname() when connecting from guest Stefano Brivio
2025-02-03 2:05 ` David Gibson
2025-02-03 6:09 ` Stefano Brivio
2025-02-03 8:59 ` David Gibson
2025-02-03 9:45 ` Stefano Brivio
2025-01-31 19:39 ` [PATCH v3 19/20] tcp: Add HOSTSIDE(x), HOSTFLOW(x) macros Stefano Brivio
2025-02-03 2:06 ` David Gibson
2025-01-31 19:39 ` [PATCH v3 20/20] Implement target side of migration Stefano Brivio
2025-02-01 7:45 ` [PATCH v3 00/20] Draft, incomplete series introducing state migration Stefano Brivio
2025-02-03 2:18 ` David Gibson
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=Z6AzzufWyCJEkAgM@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).