From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
KONRAD Frederic <frederic.konrad@adacore.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Fabien Chouteau <chouteau@adacore.com>
Subject: Re: [PATCH v2 0/3] Convert sparc devices to new ptimer API
Date: Mon, 21 Oct 2019 16:06:43 +0200 [thread overview]
Message-ID: <0ebdbde6-d804-20c1-6fa4-ad826756ff9c@redhat.com> (raw)
In-Reply-To: <20191021134357.14266-1-peter.maydell@linaro.org>
On 10/21/19 3:43 PM, Peter Maydell wrote:
> This patchset converts the devices used by sparc machines to the new
> ptimer API.
>
> Currently the ptimer design uses a QEMU bottom-half as its mechanism
> for calling back into the device model using the ptimer when the
> timer has expired. Unfortunately this design is fatally flawed,
> because it means that there is a lag between the ptimer updating its
> own state and the device callback function updating device state, and
> guest accesses to device registers between the two can return
> inconsistent device state. This was reported as a bug in a specific
> timer device but it's a problem with the generic ptimer code:
> https://bugs.launchpad.net/qemu/+bug/1777777
>
> The updates to the individual ptimer devices are straightforward:
> we need to add begin/commit calls around the various places that
> modify the ptimer state, and use the new ptimer_init() function
> to create the timer.
>
> Changes v1->v2:
> * patches 2 and 3 are the old 1 and 2 and have been reviewed
> * patch 1 is new and removes a pointless NULL check; without
> this we'd probably have got Coverity errors when patch 3
> added a use of t->timer before the check for it being NULL
>
> thanks
> --PMM
>
>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> *** BLURB HERE ***
>
> Peter Maydell (3):
> hw/timer/slavio_timer: Remove useless check for NULL t->timer
> hw/timer/grlib_gptimer.c: Switch to transaction-based ptimer API
> hw/timer/slavio_timer.c: Switch to transaction-based ptimer API
Nitpicking, maybe reorder the grlib_gptimer patch last:
hw/timer/slavio_timer: Remove useless check for NULL t->timer
hw/timer/slavio_timer.c: Switch to transaction-based ptimer API
hw/timer/grlib_gptimer.c: Switch to transaction-based ptimer API
next prev parent reply other threads:[~2019-10-21 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 13:43 [PATCH v2 0/3] Convert sparc devices to new ptimer API Peter Maydell
2019-10-21 13:43 ` [PATCH v2 1/3] hw/timer/slavio_timer: Remove useless check for NULL t->timer Peter Maydell
2019-10-21 14:03 ` Philippe Mathieu-Daudé
2019-10-21 16:24 ` Richard Henderson
2019-10-21 13:43 ` [PATCH v2 2/3] hw/timer/grlib_gptimer.c: Switch to transaction-based ptimer API Peter Maydell
2019-10-21 13:43 ` [PATCH v2 3/3] hw/timer/slavio_timer.c: " Peter Maydell
2019-10-21 14:06 ` Philippe Mathieu-Daudé [this message]
2019-10-24 12:19 ` [PATCH v2 0/3] Convert sparc devices to new " Peter Maydell
2019-10-24 18:04 ` Mark Cave-Ayland
2019-10-24 18:17 ` Philippe Mathieu-Daudé
2019-10-25 7:32 ` Peter Maydell
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=0ebdbde6-d804-20c1-6fa4-ad826756ff9c@redhat.com \
--to=philmd@redhat.com \
--cc=chouteau@adacore.com \
--cc=frederic.konrad@adacore.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).