qemu-arm.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-arm] [PATCH v10 5/7] hw/ptimer: Legalize running with delta = load = 0
Date: Fri, 15 Jan 2016 21:10:09 +0300	[thread overview]
Message-ID: <56993601.5010400@gmail.com> (raw)
In-Reply-To: <5695420E.2020709@gmail.com>

12.01.2016 21:12, Dmitry Osipenko пишет:
> 12.01.2016 06:58, Peter Crosthwaite пишет:
>> On Sat, Jan 09, 2016 at 08:39:53PM +0300, Dmitry Osipenko wrote:
>>> Currently ptimer would print error message and clear enable flag for an
>>> arming timer that has delta = load = 0. That actually could be a valid case
>>> for some hardware, like instant IRQ trigger for oneshot timer or continuous
>>> in periodic mode. Support those cases by printing error message only when
>>> period = 0.
>>>
>>
>> Isn't the continuous-periodic the same as period = 0, so if we were to really
>> support this, there should be no error message. This would simplify as we
>> can remove the conditionals of 0 period completely and rely only on the
>> too-fast clamps you add in previous patches.
>>
>
> I don't think that clamping is needed. Instead doing the ptimer_tick might be
> necessary, so ptimer user could handle that case on it own.
>
> BTW, that printf isn't quite reliable, hw_error or other way of execution abort
> should been used instead.
>
> Thanks for the comment.
>

Looking more at it, I think we should keep period = 0 forbidden. So it's treated 
as undefined behaviour and ptimer user should take care of it. If we'd want to 
handle period = 0 within ptimer, then we should also handle freq = 0, which 
implies potential ptimer VMSD version bump. Also it is uncertain what default 
behaviour should be chosen for period = 0, my guess is that pausing 
(_not_disabling_) the timer (like in freq = 0 case) should be more common among 
various hardware. If you have any thoughts on it, please let me know.

-- 
Dmitry

  reply	other threads:[~2016-01-15 18:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 17:39 [Qemu-devel] [PATCH v10 0/7] PTimer fixes/features and ARM MPTimer conversion Dmitry Osipenko
2016-01-09 17:39 ` [Qemu-devel] [PATCH v10 1/7] hw/ptimer: Fix issues caused by the adjusted timer limit value Dmitry Osipenko
2016-01-10  0:28   ` [Qemu-arm] " Peter Crosthwaite
2016-01-09 17:39 ` [Qemu-devel] [PATCH v10 2/7] hw/ptimer: Perform tick and counter wrap around if timer already expired Dmitry Osipenko
2016-01-10  0:44   ` [Qemu-arm] " Peter Crosthwaite
2016-01-10 14:09     ` Dmitry Osipenko
2016-01-20 17:03     ` Dmitry Osipenko
2016-01-20 17:22       ` [Qemu-devel] " Dmitry Osipenko
2016-01-09 17:39 ` [Qemu-devel] [PATCH v10 3/7] hw/ptimer: Update .delta on period/freq change Dmitry Osipenko
2016-01-09 17:39 ` [Qemu-arm] [PATCH v10 4/7] hw/ptimer: Support "on the fly" timer mode switch Dmitry Osipenko
2016-01-10  0:50   ` Peter Crosthwaite
2016-01-09 17:39 ` [Qemu-devel] [PATCH v10 5/7] hw/ptimer: Legalize running with delta = load = 0 Dmitry Osipenko
2016-01-12  3:58   ` [Qemu-arm] " Peter Crosthwaite
2016-01-12 18:12     ` Dmitry Osipenko
2016-01-15 18:10       ` Dmitry Osipenko [this message]
2016-01-20  0:50       ` Dmitry Osipenko
2016-01-09 17:39 ` [Qemu-arm] [PATCH v10 6/7] hw/ptimer: Introduce ptimer_get_limit Dmitry Osipenko
2016-01-12  3:59   ` [Qemu-devel] " Peter Crosthwaite
2016-01-09 17:39 ` [Qemu-arm] [PATCH v10 7/7] arm_mptimer: Convert to use ptimer Dmitry Osipenko
2016-01-10 18:05   ` Dmitry Osipenko
2016-01-10 18:12     ` Dmitry Osipenko

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=56993601.5010400@gmail.com \
    --to=digetx@gmail.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).