From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Artem Pisarenko <artem.k.pisarenko@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Fam Zheng <famz@redhat.com>,
Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>,
"open list:Block I/O path" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 2/4] Introduce attributes to qemu timer subsystem
Date: Thu, 18 Oct 2018 10:26:21 +0100 [thread overview]
Message-ID: <20181018092621.GC557@stefanha-x1.localdomain> (raw)
In-Reply-To: <c9cfbdff-f713-b49d-4ac8-33ed79b08502@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Wed, Oct 17, 2018 at 01:24:28PM +0200, Paolo Bonzini wrote:
> On 17/10/2018 12:57, Artem Pisarenko wrote:
> >> Further down in this patch the notation is QEMU_TIMER_ATTR_<id>, which I
> >> think is clearer because QEMU_TIMER_ATTR(id) looks like a (non-existent)
> >> macro. Please use the QEMU_TIMER_ATTR_<id> notation consistently.
> >
> > Yes, I've just forgot to update comments after previous patch version,
> > where it actually was macro.
> >
> >> What is the purpose of this bit? I guess it's just here as a
> >> placeholder because no real bits have been defined yet. Hopefully the
> >> next patch removes it (/* This placeholder is removed in the next patch
> >> */ would be a nice way to document this for reviewers).
> >
> > It's just to prevent compilation errors, as required by
> > https://wiki.qemu.org/Contribute/SubmitAPatch#Split_up_long_patches
> >
> >> The enum isn't needed and makes debugging harder since the bit number is
> >> implicit in the enum ordering. This alternative is clearer and more
> >> concise:
> >>
> >> #define QEMU_TIMER_ATTR_foo BIT(n)
> >
> > Agree.
>
> Like this?
Yes, something like that is good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-10-18 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 8:24 [Qemu-devel] [PATCH v2 0/4] Introduce attributes for timers subsystem and remove QEMU_CLOCK_VIRTUAL_EXT clock type Artem Pisarenko
2018-10-17 8:24 ` [Qemu-devel] [PATCH v2 1/4] Revert some patches from recent [PATCH v6] "Fixing record/replay and adding reverse debugging" Artem Pisarenko
2018-10-17 8:24 ` [Qemu-devel] [PATCH v2 2/4] Introduce attributes to qemu timer subsystem Artem Pisarenko
2018-10-17 9:12 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-10-17 9:15 ` Paolo Bonzini
2018-10-17 10:57 ` Artem Pisarenko
2018-10-17 11:24 ` Paolo Bonzini
2018-10-17 13:07 ` Artem Pisarenko
2018-10-17 14:43 ` Paolo Bonzini
2018-10-17 14:57 ` Artem Pisarenko
2018-10-18 9:26 ` Stefan Hajnoczi [this message]
2018-10-17 8:24 ` [Qemu-devel] [PATCH v2 3/4] Restores record/replay behavior related to special virtual clock processing for timers used in external subsystems Artem Pisarenko
2018-10-17 8:24 ` [Qemu-devel] [PATCH v2 4/4] Optimize record/replay checkpointing for all clocks it applies to Artem Pisarenko
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=20181018092621.GC557@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=artem.k.pisarenko@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).