From: Zenghui Yu <yuzenghui@huawei.com>
To: Marc Zyngier <maz@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Eric Auger <eric.auger@redhat.com>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] irqchip/gic-v4.1: Update effective affinity of virtual SGIs
Date: Thu, 16 Apr 2020 11:36:35 +0800 [thread overview]
Message-ID: <c2dc9d25-937c-a3ff-c6f1-b010f82187ed@huawei.com> (raw)
In-Reply-To: <20200414095013.2821418-3-maz@kernel.org>
On 2020/4/14 17:50, Marc Zyngier wrote:
> Although the vSGIs are not directly visible to the host, they still
> get moved around by the CPU hotplug, for example. This results in
> the kernel moaning on the console, such as:
>
> genirq: irq_chip GICv4.1-sgi did not update eff. affinity mask of irq 38
>
> Updating the effective affinity on set_affinity() fixes it.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Zenghui Yu <yuzenghui@huawei.com>
Thanks.
> ---
> drivers/irqchip/irq-gic-v3-its.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index e24a145f17f6..84366cc1c14f 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -4054,6 +4054,7 @@ static int its_sgi_set_affinity(struct irq_data *d,
> * not on the host (since they can only be targetting a vPE).
> * Tell the kernel we've done whatever it asked for.
> */
> + irq_data_update_effective_affinity(d, mask_val);
> return IRQ_SET_MASK_OK;
> }
>
>
prev parent reply other threads:[~2020-04-16 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 9:50 [PATCH 0/2] GICv4.1 fixes for 5.7 Marc Zyngier
2020-04-14 9:50 ` [PATCH 1/2] irqchip/gic-v4.1: Add support for VPENDBASER's Dirty+Valid signaling Marc Zyngier
2020-04-16 3:35 ` Zenghui Yu
2020-04-14 9:50 ` [PATCH 2/2] irqchip/gic-v4.1: Update effective affinity of virtual SGIs Marc Zyngier
2020-04-16 3:36 ` 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=c2dc9d25-937c-a3ff-c6f1-b010f82187ed@huawei.com \
--to=yuzenghui@huawei.com \
--cc=eric.auger@redhat.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®