From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org,
"Pavel Dovgalyuk" <Pavel.Dovgalyuk@ispras.ru>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>
Subject: Re: [PATCH v4 06/24] chardev: set record/replay on the base device of a muxed device
Date: Wed, 13 Mar 2024 00:11:44 +1000 [thread overview]
Message-ID: <CZRTZI069362.3IKMWWPX4ZO4P@wheely> (raw)
In-Reply-To: <CAJ+F1CKmgTCZfvWAfHOOAx7ne=5NFQC-pmdyvmECX3syXf9-=g@mail.gmail.com>
On Tue Mar 12, 2024 at 10:39 PM AEST, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 11, 2024 at 9:44 PM Nicholas Piggin <npiggin@gmail.com> wrote:
> >
> > chardev events to a muxed device don't get recorded because e.g.,
> > qemu_chr_be_write() checks whether the base device has the record flag
> > set.
> >
> > This can be seen when replaying a trace that has characters typed into
> > the console, an examination of the log shows they are not recorded.
> >
> > Setting QEMU_CHAR_FEATURE_REPLAY on the base chardev fixes the problem.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > chardev/char.c | 71 +++++++++++++++++++++++++++++++++++---------------
> > 1 file changed, 50 insertions(+), 21 deletions(-)
> >
> > diff --git a/chardev/char.c b/chardev/char.c
> > index 3c43fb1278..ba847b6e9e 100644
> > --- a/chardev/char.c
> > +++ b/chardev/char.c
> > @@ -615,11 +615,24 @@ ChardevBackend *qemu_chr_parse_opts(QemuOpts *opts, Error **errp)
> > return backend;
> > }
> >
> > -Chardev *qemu_chr_new_from_opts(QemuOpts *opts, GMainContext *context,
> > - Error **errp)
> > +static void qemu_chardev_set_replay(Chardev *chr, Error **errp)
> > +{
> > + if (replay_mode != REPLAY_MODE_NONE) {
> > + if (CHARDEV_GET_CLASS(chr)->chr_ioctl) {
> > + error_setg(errp, "Replay: ioctl is not supported "
> > + "for serial devices yet");
> > + return;
>
> You are changing the behaviour, the previous code was just printing an
> error, but let it go. I think you should make this a separate change.
Ah yes true, I will change.
>
> > + }
> > + qemu_chr_set_feature(chr, QEMU_CHAR_FEATURE_REPLAY);
> > + replay_register_char_driver(chr);
> > + }
> > +}
> > +
> > +static Chardev *__qemu_chr_new_from_opts(QemuOpts *opts, GMainContext *context,
> > + bool replay, Error **errp)
>
> Having so many chr_new functions is starting to really damage
> readability. Also don't use '__' prefix for global symbols, they are
> reserved.
Yeah I agree they're not good, I tried to think of a better name.
>
> > {> const ChardevClass *cc;
> > - Chardev *chr = NULL;
> > + Chardev *base = NULL, *chr = NULL;
> > ChardevBackend *backend = NULL;
> > const char *name = qemu_opt_get(opts, "backend");
> > const char *id = qemu_opts_id(opts);
> > @@ -657,11 +670,11 @@ Chardev *qemu_chr_new_from_opts(QemuOpts *opts, GMainContext *context,
> > chr = qemu_chardev_new(bid ? bid : id,
> > object_class_get_name(OBJECT_CLASS(cc)),
> > backend, context, errp);
> > -
> > if (chr == NULL) {
> > goto out;
> > }
> >
> > + base = chr;
> > if (bid) {
> > Chardev *mux;
> > qapi_free_ChardevBackend(backend);
> > @@ -681,11 +694,25 @@ Chardev *qemu_chr_new_from_opts(QemuOpts *opts, GMainContext *context,
> > out:
> > qapi_free_ChardevBackend(backend);
> > g_free(bid);
> > +
> > + if (replay && base) {
> > + /* RR should be set on the base device, not the mux */
> > + qemu_chardev_set_replay(base, errp);
> > + }
> > +
> > return chr;
> > }
> >
> > -Chardev *qemu_chr_new_noreplay(const char *label, const char *filename,
> > - bool permit_mux_mon, GMainContext *context)
> > +Chardev *qemu_chr_new_from_opts(QemuOpts *opts, GMainContext *context,
> > + Error **errp)
> > +{
> > + /* XXX: should this really not record/replay? */
>
> I don't understand the context here, make it a different commit to explain?
Good point. I was wondering whether devices created by this
call should have record/replay enabled.
>
> > + return __qemu_chr_new_from_opts(opts, context, false, errp);
> > +}
> > +
> > +static Chardev *__qemu_chr_new(const char *label, const char *filename,
> > + bool permit_mux_mon, GMainContext *context,
> > + bool replay)
> > {
> > const char *p;
> > Chardev *chr;
> > @@ -693,14 +720,22 @@ Chardev *qemu_chr_new_noreplay(const char *label, const char *filename,
> > Error *err = NULL;
> >
> > if (strstart(filename, "chardev:", &p)) {
> > - return qemu_chr_find(p);
> > + chr = qemu_chr_find(p);
> > + if (replay) {
> > + qemu_chardev_set_replay(chr, &err);
> > + if (err) {
> > + error_report_err(err);
> > + return NULL;
> > + }
> > + }
> > + return chr;
> > }
> >
> > opts = qemu_chr_parse_compat(label, filename, permit_mux_mon);
> > if (!opts)
> > return NULL;
> >
> > - chr = qemu_chr_new_from_opts(opts, context, &err);
> > + chr = __qemu_chr_new_from_opts(opts, context, replay, &err);
> > if (!chr) {
> > error_report_err(err);
> > goto out;
> > @@ -722,24 +757,18 @@ out:
> > return chr;
> > }
> >
> > +Chardev *qemu_chr_new_noreplay(const char *label, const char *filename,
> > + bool permit_mux_mon, GMainContext *context)
> > +{
> > + return __qemu_chr_new(label, filename, permit_mux_mon, context, false);
> > +}
> > +
> > static Chardev *qemu_chr_new_permit_mux_mon(const char *label,
> > const char *filename,
> > bool permit_mux_mon,
> > GMainContext *context)
> > {
> > - Chardev *chr;
> > - chr = qemu_chr_new_noreplay(label, filename, permit_mux_mon, context);
> > - if (chr) {
> > - if (replay_mode != REPLAY_MODE_NONE) {
> > - qemu_chr_set_feature(chr, QEMU_CHAR_FEATURE_REPLAY);
> > - }
> > - if (qemu_chr_replay(chr) && CHARDEV_GET_CLASS(chr)->chr_ioctl) {
> > - error_report("Replay: ioctl is not supported "
> > - "for serial devices yet");
> > - }
> > - replay_register_char_driver(chr);
> > - }
> > - return chr;
> > + return __qemu_chr_new(label, filename, permit_mux_mon, context, true);
> > }
> >
> > Chardev *qemu_chr_new(const char *label, const char *filename,
> > --
> > 2.42.0
> >
> >
>
> It's probably too late for 9.0, splitting the patch and preliminary
> cleanup should really help reviewing the change and pointing out the
> behaviour differences.
Agree. Fixing the rr flag setting could be considered a bug fix.
So a minimal patch that does not change other behaviour might be
suitable for 9.0. But that could be decided at the time, no need
to rush this in before the soft freeze.
Thanks,
Nick
next prev parent reply other threads:[~2024-03-12 14:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 17:40 [PATCH v4 00/24] replay: fixes and new test cases Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 01/24] scripts/replay-dump.py: Update to current rr record format Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 02/24] scripts/replay-dump.py: rejig decoders in event number order Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 03/24] tests/avocado: excercise scripts/replay-dump.py in replay tests Nicholas Piggin
2024-03-12 13:25 ` Alex Bennée
2024-03-11 17:40 ` [PATCH v4 04/24] replay: allow runstate shutdown->running when replaying trace Nicholas Piggin
2024-03-12 13:26 ` Alex Bennée
2024-03-11 17:40 ` [PATCH v4 05/24] Revert "replay: stop us hanging in rr_wait_io_event" Nicholas Piggin
2024-03-12 13:33 ` Alex Bennée
2024-03-12 14:03 ` Nicholas Piggin
2024-03-12 21:03 ` Alex Bennée
2024-03-13 5:27 ` Nicholas Piggin
2024-03-14 5:19 ` Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 06/24] chardev: set record/replay on the base device of a muxed device Nicholas Piggin
2024-03-12 12:39 ` Marc-André Lureau
2024-03-12 14:11 ` Nicholas Piggin [this message]
2024-03-11 17:40 ` [PATCH v4 07/24] replay: Fix migration use of clock Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 08/24] replay: Fix migration replay_mutex locking Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 09/24] virtio-net: Use replay_schedule_bh_event for bhs that affect machine state Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 10/24] virtio-net: Use virtual time for RSC timers Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 11/24] net: Use virtual time for net announce Nicholas Piggin
2024-03-12 9:09 ` Pavel Dovgalyuk
2024-03-12 11:05 ` Nicholas Piggin
2024-03-12 11:12 ` Pavel Dovgalyuk
2024-03-13 5:38 ` Nicholas Piggin
2024-03-13 7:09 ` Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 12/24] savevm: Fix load_snapshot error path crash Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 13/24] tests/avocado: replay_linux.py remove the timeout expected guards Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 14/24] tests/avocado/reverse_debugging.py: mark aarch64 and pseries as not flaky Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 15/24] tests/avocado: reverse_debugging.py add test for x86-64 q35 machine Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 16/24] tests/avocado: reverse_debugging.py verify addresses between record and replay Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 17/24] tests/avocado: reverse_debugging.py stop VM before sampling icount Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 18/24] tests/avocado: reverse_debugging reverse-step at the end of the trace Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 19/24] tests/avocado: reverse_debugging.py add snapshot testing Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 20/24] replay: simple auto-snapshot mode for record Nicholas Piggin
2024-03-12 9:00 ` Pavel Dovgalyuk
2024-03-12 10:43 ` Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 21/24] tests/avocado: reverse_debugging.py test auto-snapshot mode Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 22/24] target/ppc: fix timebase register reset state Nicholas Piggin
2024-03-12 13:24 ` Alex Bennée
2024-03-12 13:47 ` Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 23/24] spapr: Fix vpa dispatch count for record-replay Nicholas Piggin
2024-03-11 17:40 ` [PATCH v4 24/24] tests/avocado: replay_linux.py add ppc64 pseries test Nicholas Piggin
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=CZRTZI069362.3IKMWWPX4ZO4P@wheely \
--to=npiggin@gmail.com \
--cc=Pavel.Dovgalyuk@ispras.ru \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wainersm@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.
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).