qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Leonid Komarianskyi <Leonid_Komarianskyi@epam.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
	 Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Dmytro Firsov <Dmytro_Firsov@epam.com>
Subject: Re: [PATCH v2] target/arm: Add overflow check for gt_recalc_timer
Date: Mon, 20 Nov 2023 17:40:15 +0000	[thread overview]
Message-ID: <CAFEAcA_auQOuPyZMbGd2G6ePn60nnPLtm5N+jRGz1bTvsg5Scg@mail.gmail.com> (raw)
In-Reply-To: <baafd137-58de-42e9-9f06-c7f7789d4b77@epam.com>

On Thu, 9 Nov 2023 at 15:14, Leonid Komarianskyi
<Leonid_Komarianskyi@epam.com> wrote:
>
> Peter Maydell, thank you for your comments.
> I apologize for so late response - returned to this issue and now I will
> answer faster. I fixed the commit according to your recommendations,
> please take a look at the new version.
>
>  > There is also a comment or two from me in the bug report pointing
>  > out that the handling of wraparound is also wrong in the other
>  > half of this if(); we should look at that too.
>
> I read this topic and as I understand changing the other half of "if" is
> not related to the reported issue. Since it affects running virtualized
> setups on arm64 QEMU, e.g. Zephyr
> (https://github.com/zephyrproject-rtos/zephyr/blob/main//boards/arm64/xenvm/doc/index.rst)
> maybe is it worth merging at least this change?

I feel they're really pretty much the same thing -- when we
added support for the timer offset registers we didn't correctly
update the arithmetic that calculates when the next interrupt
line transition happens.

I've just posted my version of a patch that I think should
fix both halves of the if():

https://patchew.org/QEMU/20231120173506.3729884-1-peter.maydell@linaro.org/

Thanks for prodding me into looking at this issue again -- I had
somehow got the mistaken impression that it only happened in
some weird icount sleep=off situations.

thanks
-- PMM


      reply	other threads:[~2023-11-20 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 15:16 [PATCH] target/arm: Add overflow check for gt_recalc_timer Leonid Komarianskyi
2023-04-13 13:24 ` Peter Maydell
2023-11-09 13:55   ` [PATCH v2] " Leonid Komarianskyi
2023-11-09 15:13     ` Leonid Komarianskyi
2023-11-20 17:40       ` Peter Maydell [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=CAFEAcA_auQOuPyZMbGd2G6ePn60nnPLtm5N+jRGz1bTvsg5Scg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=Dmytro_Firsov@epam.com \
    --cc=Leonid_Komarianskyi@epam.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --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).