From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: "chenxiang (M)" <chenxiang66@hisilicon.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: vgic-v4: Consistently request doorbell irq for blocking vCPU
Date: Thu, 13 Jul 2023 08:11:00 +0100 [thread overview]
Message-ID: <87a5w09th7.wl-maz@kernel.org> (raw)
In-Reply-To: <ZK+TQ7qRK51N1n7g@thinky-boi>
On Thu, 13 Jul 2023 07:01:39 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> On Thu, Jul 13, 2023 at 01:57:46PM +0800, chenxiang (M) wrote:
> > > Of course, it is totally untested... ;-) But I like that the doorbell
> > > request is solely driven by the WFI state, and we avoid leaking the
> > > knowledge outside of the vgic code.
> >
> > I have tested this approach and it also solves the issue. Please feel free
> > to add:
> > Tested-by: Xiang Chen <chenxiang66@hisilicon.com>
>
> Excellent, thanks for testing a couple of iterations for us here. Marc,
> do you want to add a changelog to this?
Done [1]. I've nicked most of your changelog, so you get a CDB tag ;-)
Thanks,
M.
[1] https://lore.kernel.org/all/20230713070657.3873244-1-maz@kernel.org/
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-07-13 7:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 17:55 [PATCH] KVM: arm64: vgic-v4: Consistently request doorbell irq for blocking vCPU Oliver Upton
2023-07-11 7:23 ` Marc Zyngier
2023-07-11 7:26 ` Oliver Upton
2023-07-11 7:57 ` Marc Zyngier
2023-07-12 12:09 ` Zenghui Yu
2023-07-12 13:49 ` Marc Zyngier
2023-07-12 15:56 ` Zenghui Yu
2023-07-13 2:38 ` chenxiang (M)
2023-07-12 20:14 ` Oliver Upton
2023-07-13 5:57 ` chenxiang (M)
2023-07-13 6:01 ` Oliver Upton
2023-07-13 7:11 ` Marc Zyngier [this message]
2023-07-11 20:00 ` Oliver Upton
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=87a5w09th7.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=chenxiang66@hisilicon.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.