qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v7 0/2] PTimer fix and ARM MPTimer conversion
Date: Sat, 31 Oct 2015 01:44:03 +0300	[thread overview]
Message-ID: <5633F2B3.2000406@gmail.com> (raw)
In-Reply-To: <CAFEAcA_WTSyu3LjdsgmdF=-4gO2eStrY0EzFEKJVorwLNYPi3Q@mail.gmail.com>

31.10.2015 00:52, Peter Maydell пишет:
> On 24 October 2015 at 13:21, Dmitry Osipenko <digetx@gmail.com> wrote:
>> Changelog for ARM MPTimer QEMUTimer to ptimer conversion:
>>
>>      V2: Fixed changing periodic timer counter value "on the fly". I added a
>>          test to the gist to cover that issue.
>>
>>      V3: Fixed starting the timer with load = 0 and counter != 0, added tests
>>          to the gist for this issue. Changed vmstate version for all VMSD's,
>>          since loadvm doesn't check version of nested VMSD.
>>
>>      V4: Fixed spurious IT bit set for the timer starting in the periodic mode
>>          with counter = 0. Test added.
>>
>>      V5: Code cleanup, now depends on ptimer_set_limit() fix.
>>
>>      V6: No code change, added test to check ptimer_get_count() with corrected
>>          .limit value.
>>
>>      V7: No change.
>>
>> ARM MPTimer tests: https://gist.github.com/digetx/dbd46109503b1a91941a
>
> Hi. Given that we're now in the second half of softfreeze, and
> the discussions about the design of the changes to ptimer don't
> seem to have reached a conclusion yet, I would prefer to defer
> this to 2.6. (It feels a bit late in the release cycle to make changes
> to a core component like ptimer that affects multiple boards.)

Sure, I have no objections.

> My understanding is that although this patchset fixes a bunch of
> edge cases and odd features in the mptimer, there aren't any bugs
> that it fixes that cause problems for common guests like Linux, right?
>

Yes, it should be alright.

-- 
Dmitry

      reply	other threads:[~2015-10-30 22:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 12:21 [Qemu-devel] [PATCH v7 0/2] PTimer fix and ARM MPTimer conversion Dmitry Osipenko
2015-10-24 12:21 ` [Qemu-devel] [PATCH v7 1/2] hw/ptimer: Fix issues caused by artificially limited timer timeout Dmitry Osipenko
2015-10-24 19:45   ` Peter Crosthwaite
2015-10-24 22:22     ` Dmitry Osipenko
2015-10-24 23:55       ` Peter Crosthwaite
2015-10-25 13:23         ` Dmitry Osipenko
2015-10-25 17:39           ` Peter Crosthwaite
2015-10-27 21:26             ` Dmitry Osipenko
2015-10-29  1:39               ` Peter Crosthwaite
2015-10-29 14:28                 ` Dmitry Osipenko
2015-10-30 16:14                   ` Dmitry Osipenko
2015-10-24 12:22 ` [Qemu-devel] [PATCH v7 2/2] arm_mptimer: Convert to use ptimer Dmitry Osipenko
2015-10-30 21:52 ` [Qemu-devel] [PATCH v7 0/2] PTimer fix and ARM MPTimer conversion Peter Maydell
2015-10-30 22:44   ` Dmitry Osipenko [this message]

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=5633F2B3.2000406@gmail.com \
    --to=digetx@gmail.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=peter.maydell@linaro.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).