From: Marcelo Tosatti <mtosatti@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: gleb@kernel.org, pbonzini@redhat.com, qemu-devel@nongnu.org,
armbru@redhat.com, mprivozn@redhat.com
Subject: Re: [Qemu-devel] [patch 1/3] mc146818rtc: add rtc_reset_reinjection QMP command
Date: Mon, 2 Jun 2014 17:20:38 -0300 [thread overview]
Message-ID: <20140602202038.GA12036@amt.cnet> (raw)
In-Reply-To: <538CD111.30604@redhat.com>
On Mon, Jun 02, 2014 at 01:31:29PM -0600, Eric Blake wrote:
> On 06/02/2014 11:51 AM, mtosatti@redhat.com wrote:
> > It is necessary to reset RTC interrupt reinjection backlog if
> > guest time is synchronized via a different mechanism, such as
> > QGA's guest-set-time command.
> >
> > Failing to do so causes both corrections to be applied (summed),
> > resulting in an incorrect guest time.
> >
> > Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> >
> > Index: qemu/hw/timer/mc146818rtc.c
>
> Still no --- separator between your commit message and the patch body.
> Are you using 'git send-email'?
OK, diffstats on every patch.
> > Index: qemu/qapi-schema.json
> > ===================================================================
> > --- qemu.orig/qapi-schema.json
> > +++ qemu/qapi-schema.json
> > @@ -4722,3 +4722,15 @@
> > 'btn' : 'InputBtnEvent',
> > 'rel' : 'InputMoveEvent',
> > 'abs' : 'InputMoveEvent' } }
> > +
> > +##
> > +# @: rtc-reset-reinjection
>
> s/: // to resemble most other commands
Several commands have ":". What is the correct syntax and why?
> > +# This command will reset RTC's interrupt reinjection backlog.
>
> s/RTC's/the RTC/
>
> > +# Can be used if another mechanism to synchronize guest time
> > +# is in effect, for example QEMU guest agents guest-set-time
>
> s/agents/agent's/
Fixed.
> > +# command.
> > +#
> > +# Since: 2.1
> > +##
> > +{ 'command': 'rtc-reset-reinjection' }
> > Index: qemu/qmp-commands.hx
> > ===================================================================
> > --- qemu.orig/qmp-commands.hx
> > +++ qemu/qmp-commands.hx
> > @@ -3572,3 +3572,26 @@ Example:
> > } } ] }
> >
> > EQMP
> > +
> > +#if defined (TARGET_I386)
> > + {
> > + .name = "rtc_reset_reinjection",
>
> s/rtc_reset_reinjection/rtc-reset-reinjection/
This is a function name.
next prev parent reply other threads:[~2014-06-02 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140530201145.194061806@amt.cnet>
2014-06-02 17:51 ` [Qemu-devel] [patch 0/3] add QMP command to reset rtc interrupt backlog (v3) mtosatti
2014-06-02 17:51 ` [Qemu-devel] [patch 1/3] mc146818rtc: add rtc_reset_reinjection QMP command mtosatti
2014-06-02 19:31 ` Eric Blake
2014-06-02 20:20 ` Marcelo Tosatti [this message]
2014-06-02 20:31 ` Eric Blake
2014-06-02 17:51 ` [Qemu-devel] [patch 2/3] add object_property_add_alias mtosatti
2014-06-02 17:51 ` [Qemu-devel] [patch 3/3] mc146818rtc: add "rtc" link to "/machine" mtosatti
2014-06-02 19:05 ` [Qemu-devel] [patch 0/3] add QMP command to reset rtc interrupt backlog (v3) Eric Blake
2014-06-02 19:20 ` Marcelo Tosatti
2014-06-02 19:41 ` Eric Blake
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=20140602202038.GA12036@amt.cnet \
--to=mtosatti@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=gleb@kernel.org \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).