qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: dave@treblig.org, armbru@redhat.com, pbonzini@redhat.com,
	marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH for-11.0 0/5] some improvements around error reporting
Date: Thu, 27 Nov 2025 20:51:18 +0000	[thread overview]
Message-ID: <aSi5xrJrlI9W_MJk@redhat.com> (raw)
In-Reply-To: <20251127173352.283731-1-vsementsov@yandex-team.ru>

On Thu, Nov 27, 2025 at 08:33:47PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all. The main thing I wanted to do is to enable timestamps
> for errer_report() and friends when QMP monitor is active.
> Analyzing logs without timestamps is painful.
> 
> And some enhancements here and there around.

This is significantly overlapping  with what I've been working on here:

  https://lists.nongnu.org/archive/html/qemu-devel/2025-09/msg05222.html

I had to pause that temporarily but intend to post a v5 for 11.0 dev
cycle

> 
> Vladimir Sementsov-Ogievskiy (5):
>   ui/vnc: don't use of error_printf_unless_qmp()
>   monitor: remove unused error_printf_unless_qmp() function
>   monitor: rework monitor_cur_is_qmp() into monitor_cur_is_hmp()
>   error: print error_report timestamp when QMP monitor is active
>   error-report: fix doc for vreport()
> 
>  include/monitor/monitor.h      |  5 +----
>  monitor/monitor.c              | 30 +++---------------------------
>  stubs/error-printf.c           |  5 -----
>  stubs/monitor-core.c           |  5 +++++
>  tests/unit/test-util-sockets.c |  1 +
>  ui/vnc.c                       |  9 ++++-----
>  util/error-report.c            | 25 +++++++++++++++----------
>  7 files changed, 29 insertions(+), 51 deletions(-)
> 
> -- 
> 2.48.1
> 
> 

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2025-11-27 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 17:33 [PATCH for-11.0 0/5] some improvements around error reporting Vladimir Sementsov-Ogievskiy
2025-11-27 17:33 ` [PATCH 1/5] ui/vnc: don't use of error_printf_unless_qmp() Vladimir Sementsov-Ogievskiy
2025-11-27 17:33 ` [PATCH 2/5] monitor: remove unused error_printf_unless_qmp() function Vladimir Sementsov-Ogievskiy
2025-11-27 17:33 ` [PATCH 3/5] monitor: rework monitor_cur_is_qmp() into monitor_cur_is_hmp() Vladimir Sementsov-Ogievskiy
2025-11-27 17:33 ` [PATCH 4/5] error: print error_report timestamp when QMP monitor is active Vladimir Sementsov-Ogievskiy
2025-11-27 17:33 ` [PATCH 5/5] error-report: fix doc for vreport() Vladimir Sementsov-Ogievskiy
2025-11-27 20:51 ` Daniel P. Berrangé [this message]
2025-11-28 10:23   ` [PATCH for-11.0 0/5] some improvements around error reporting Vladimir Sementsov-Ogievskiy

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=aSi5xrJrlI9W_MJk@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dave@treblig.org \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    /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).