qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zenghui Yu <zenghui.yu@linux.dev>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] hw/intc/arm_gicv3_kvm: two small fixes about register accesses
Date: Wed, 6 Aug 2025 22:55:05 +0800	[thread overview]
Message-ID: <9806e26b-e4cc-4617-868a-0e09101a802b@linux.dev> (raw)
In-Reply-To: <CAFEAcA-dRAViFBSvmYS+FSMKPhP_ej5Sv90n6+WLaR=jeQeiAg@mail.gmail.com>

On 2025/8/1 01:11, Peter Maydell wrote:
> On Tue, 29 Jul 2025 at 17:17, Zenghui Yu <zenghui.yu@linux.dev> wrote:
> >
> > Zenghui Yu (2):
> >   hw/intc/arm_gicv3_kvm: Remove writes to ICPENDR registers
> >   hw/intc/arm_gicv3_kvm: Write all 1's to clear enable/active
> >
> >  hw/intc/arm_gicv3_kvm.c | 6 ++----
> >  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> Did this cause any visible bugs, or did you just notice it
> by code inspection ?

They're noticed by code inspection. I agree with that patch #2 is
guest-visible only when doing a system reset.

> 
> Applied to target-arm.next, thanks.

Thanks!

Zenghui


      reply	other threads:[~2025-08-06 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 16:16 [PATCH 0/2] hw/intc/arm_gicv3_kvm: two small fixes about register accesses Zenghui Yu
2025-07-29 16:16 ` [PATCH 1/2] hw/intc/arm_gicv3_kvm: Remove writes to ICPENDR registers Zenghui Yu
2025-07-31 16:42   ` Peter Maydell
2025-07-31 17:01     ` Peter Maydell
2025-07-29 16:16 ` [PATCH 2/2] hw/intc/arm_gicv3_kvm: Write all 1's to clear enable/active Zenghui Yu
2025-07-31 16:59   ` Peter Maydell
2025-08-06 15:01     ` Zenghui Yu
2025-07-31 17:11 ` [PATCH 0/2] hw/intc/arm_gicv3_kvm: two small fixes about register accesses Peter Maydell
2025-08-06 14:55   ` Zenghui Yu [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=9806e26b-e4cc-4617-868a-0e09101a802b@linux.dev \
    --to=zenghui.yu@linux.dev \
    --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).