From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type
Date: Fri, 8 Jun 2018 11:54:04 +0800 [thread overview]
Message-ID: <20180608035404.GV750@xz-mi> (raw)
In-Reply-To: <878t7qu0o9.fsf@dusky.pond.sub.org>
On Thu, Jun 07, 2018 at 04:32:54PM +0200, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > Instead, use a dynamic function to detect which clock we'll use. The
> > problem is that the old code will let monitor initialization depends on
> > qtest_enabled(). After this change, we don't have such a dependency any
> > more.
> >
> > Suggested-by: Markus Armbruster <armbru@redhat.com>
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > monitor.c | 21 ++++++++++++---------
> > 1 file changed, 12 insertions(+), 9 deletions(-)
> >
> > diff --git a/monitor.c b/monitor.c
> > index 2504696d76..bd9ab5597f 100644
> > --- a/monitor.c
> > +++ b/monitor.c
> > @@ -282,8 +282,6 @@ QmpCommandList qmp_commands, qmp_cap_negotiation_commands;
> >
> > Monitor *cur_mon;
> >
> > -static QEMUClockType event_clock_type = QEMU_CLOCK_REALTIME;
> > -
> > static void monitor_command_cb(void *opaque, const char *cmdline,
> > void *readline_opaque);
> >
> > @@ -310,6 +308,15 @@ static inline bool monitor_is_hmp_non_interactive(const Monitor *mon)
> > return !monitor_is_qmp(mon) && !monitor_uses_readline(mon);
> > }
> >
> > +static inline QEMUClockType monitor_get_clock(void)
> > +{
> > + if (qtest_enabled()) {
> > + return QEMU_CLOCK_VIRTUAL;
> > + } else {
> > + return QEMU_CLOCK_REALTIME;
> > + }
>
> Suggest the more laconic
>
> return qtest_enabled() ? QEMU_CLOCK_VIRTUAL : QEMU_CLOCK_REALTIME;
>
> A comment explaining why we want QEMU_CLOCK_VIRTUAL would be nice.
Will do.
--
Peter Xu
next prev parent reply other threads:[~2018-06-08 3:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 5:57 [Qemu-devel] [PATCH v9 0/7] monitor: let Monitor be thread safe Peter Xu
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 1/7] monitor: rename out_lock to mon_lock Peter Xu
2018-06-07 14:24 ` Markus Armbruster
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 2/7] monitor: protect mon->fds with mon_lock Peter Xu
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 3/7] monitor: more comments on lock-free elements Peter Xu
2018-05-30 16:26 ` Stefan Hajnoczi
2018-06-07 14:26 ` Markus Armbruster
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 4/7] monitor: fix comment for monitor_lock Peter Xu
2018-05-30 16:29 ` Stefan Hajnoczi
2018-06-07 14:27 ` Markus Armbruster
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type Peter Xu
2018-05-30 16:35 ` Stefan Hajnoczi
2018-05-31 4:11 ` Peter Xu
2018-05-31 8:23 ` Stefan Hajnoczi
2018-05-31 8:30 ` Peter Xu
2018-06-07 14:32 ` Markus Armbruster
2018-06-08 3:54 ` Peter Xu [this message]
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 6/7] monitor: move init global earlier Peter Xu
2018-05-30 16:37 ` Stefan Hajnoczi
2018-06-07 14:33 ` Markus Armbruster
2018-05-29 5:57 ` [Qemu-devel] [PATCH v9 7/7] monitor: add lock to protect mon_fdsets Peter Xu
2018-05-30 16:39 ` Stefan Hajnoczi
2018-06-07 14:38 ` Markus Armbruster
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=20180608035404.GV750@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.