All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Zhou Wang <wangzhou1@hisilicon.com>
Cc: <kvmarm@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
	<oliver.upton@linux.dev>, <tangnianyao@huawei.com>,
	<wangwudi@hisilicon.com>, <liuyonglong@huawei.com>,
	<prime.zeng@hisilicon.com>
Subject: Re: [PATCH v2 0/4] Add workaround for HIP10/HIP10C erratum 162200802
Date: Fri, 19 Sep 2025 16:52:55 +0100	[thread overview]
Message-ID: <87wm5uxwvc.wl-maz@kernel.org> (raw)
In-Reply-To: <fc7763d5-bed6-ace6-ace8-a50c031cab36@hisilicon.com>

On Mon, 01 Sep 2025 11:55:49 +0100,
Zhou Wang <wangzhou1@hisilicon.com> wrote:
> 
> On 2025/8/25 10:39, Zhou Wang wrote:
> > As the discussion from V1 series, V2 series firstly adds GICD.num_LPIs
> > writable support, then add HiSilicon erratum 162200802.
> > 
> > Erratum number should be 162200802, make a mistake in V1, so fix it as
> > well.
> > 
> > Zhou Wang (4):
> >   KVM: arm64: Allow userspace to write GICD_TYPER.num_LPIs
> >   KVM: arm64: selftests: Add test for GICD.num_LPIs
> >   Documentation: KVM: arm64: Add GICD_TYPER.num_LPIs writable
> >     description
> >   ARM64: errata: Add workaround for HIP10/HIP10C erratum 162200802
> 
> Hi Marc and Oliver,
> 
> As the discussion in V1 series, this series firstly adds GICD.num_LPIs
> writable support, then add erratum patch.

Given the state of this HW (as per [1]), I'd rather we start by
working out the strategy at the GIC level, rather than exposing stuff
to userspace before we agree on a way to make it work in the kernel.

Thanks,

	M.

[1] https://lore.kernel.org/r/20250909110615.129179-1-wangzhou1@hisilicon.com

-- 
Jazz isn't dead. It just smells funny.

  reply	other threads:[~2025-09-19 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  2:39 [PATCH v2 0/4] Add workaround for HIP10/HIP10C erratum 162200802 Zhou Wang
2025-08-25  2:39 ` [PATCH v2 1/4] KVM: arm64: Allow userspace to write GICD_TYPER.num_LPIs Zhou Wang
2025-08-25  2:39 ` [PATCH v2 2/4] KVM: arm64: selftests: Add test for GICD.num_LPIs Zhou Wang
2025-08-25  2:39 ` [PATCH v2 3/4] Documentation: KVM: arm64: Add GICD_TYPER.num_LPIs writable description Zhou Wang
2025-08-25  2:39 ` [PATCH v2 4/4] ARM64: errata: Add workaround for HIP10/HIP10C erratum 162200802 Zhou Wang
2025-09-01 10:55 ` [PATCH v2 0/4] " Zhou Wang
2025-09-19 15:52   ` Marc Zyngier [this message]
2025-09-26  7:15     ` Zhou Wang
2025-09-26  8:57       ` Marc Zyngier
2025-09-26 11:28         ` Zhou Wang

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=87wm5uxwvc.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liuyonglong@huawei.com \
    --cc=oliver.upton@linux.dev \
    --cc=prime.zeng@hisilicon.com \
    --cc=tangnianyao@huawei.com \
    --cc=wangwudi@hisilicon.com \
    --cc=wangzhou1@hisilicon.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.