From: Paolo Bonzini <pbonzini@redhat.com>
To: Artem Pisarenko <artem.k.pisarenko@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] Fix and improve core RTC function and documentation
Date: Thu, 18 Oct 2018 16:47:38 +0200 [thread overview]
Message-ID: <b29d3807-6ae3-94c6-aab3-af872a075eb7@redhat.com> (raw)
In-Reply-To: <cover.1539846575.git.artem.k.pisarenko@gmail.com>
On 18/10/2018 09:12, Artem Pisarenko wrote:
> Modifications are motivated by bug https://bugs.launchpad.net/qemu/+bug/1797033 I've encountered recently.
>
> Trying to fix it and analyzing its effect on all use cases (not covered in bug report) revealed much deeper problems.
> This is my first patch to QEMU and I'm not sure whether the way I addressed them is proper.
> They definitely require either modifications to current implementation (breaking compability), or adding clarifications to user documentation. I've tried to find compromise.
> Changes I propose are driven mostly by my interpretation of user documentation and comments in code, rather than by existing implementation.
>
> I've splitted patches in a way that at least some of them may be accepted. Following subsets are make sense on their own:
> - 1
> - 1,2,3
>
> I limited refactoring only to vl.c, although it leads to reworking of all hw/* rtc models which have unreasonable duplications of actions performed by vl.c.
> I'm sure such kind of rework will reveal more hidden bugs/features, but so far I've had enough (it's a long story how muсh effort and pain cost me to find that tricky bug above).
> I suppose just to draw attention of relevant hw/* maintainers.
Queued, thanks.
As a start of future refactoring, would you mind moving all this code to
hw/timer/rtc.c or rtc.c? It was somewaht generic before, but now it's
very tied to -rtc.
Paolo
>
> v3 changes:
> - commit messages rewritten/shortened/wrapped to match patch requirements
> - fixed minor typo
> v2 changes:
> - fixed compiler warning caused non-debug build fail
>
>
> Artem Pisarenko (4):
> vl: improve/fix documentation related to RTC function
> vl: refactor -rtc option references
> Fixes RTC bug with base datetime shifts in clock=vm
> vl,qapi: offset calculation in RTC_CHANGE event reverted
>
> qapi/misc.json | 3 +-
> qemu-options.hx | 14 +++++---
> vl.c | 105 +++++++++++++++++++++++++++++++++++++-------------------
> 3 files changed, 80 insertions(+), 42 deletions(-)
>
next prev parent reply other threads:[~2018-10-18 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 7:12 [Qemu-devel] [PATCH v3 0/4] Fix and improve core RTC function and documentation Artem Pisarenko
2018-10-18 7:12 ` [Qemu-devel] [PATCH v3 1/4] vl: improve/fix documentation related to RTC function Artem Pisarenko
2018-10-18 14:36 ` Paolo Bonzini
2018-10-18 7:12 ` [Qemu-devel] [PATCH v3 2/4] vl: refactor -rtc option references Artem Pisarenko
2018-10-18 7:12 ` [Qemu-devel] [PATCH v3 3/4] Fixes RTC bug with base datetime shifts in clock=vm Artem Pisarenko
2018-10-18 14:44 ` Paolo Bonzini
2018-10-18 7:12 ` [Qemu-devel] [PATCH v3 4/4] vl, qapi: offset calculation in RTC_CHANGE event reverted Artem Pisarenko
2018-10-18 14:47 ` Paolo Bonzini [this message]
2018-10-19 5:24 ` [Qemu-devel] [PATCH v3 0/4] Fix and improve core RTC function and documentation 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=b29d3807-6ae3-94c6-aab3-af872a075eb7@redhat.com \
--to=pbonzini@redhat.com \
--cc=artem.k.pisarenko@gmail.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).