mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: Marc Zyngier <maz@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	John Garry <john.garry@huawei.com>,
	David Decotigny <ddecotig@google.com>
Subject: Re: [PATCH v2 0/3] genirq: Managed affinity fixes
Date: Wed, 23 Mar 2022 11:52:46 +0800	[thread overview]
Message-ID: <a83da394-dcc0-c9a6-1569-9c30fbc291fd@huawei.com> (raw)
In-Reply-To: <20220321193608.975495-1-maz@kernel.org>

Hi, Marc

On 2022/3/22 3:36, Marc Zyngier wrote:
> John (and later on David) reported[1] a while ago that booting with
> maxcpus=1, managed affinity devices would fail to get the interrupts
> that were associated with offlined CPUs.
> 
> Similarly, Xiongfeng reported[2] that the GICv3 ITS would sometime use
> non-housekeeping CPUs instead of the affinity that was passed down as
> a parameter.
> 
> [1] can be fixed by not trying to activate these interrupts if no CPU
> that can satisfy the affinity is present (a patch addressing this was
> already posted[3])
> 
> [2] is a consequence of affinities containing non-online CPUs being
> passed down to the interrupt controller driver and the ITS driver
> trying to paper over that by ignoring the affinity parameter and doing
> its own (stupid) thing. It would be better to (a) get the core code to
> remove the offline CPUs from the affinity mask at all times, and (b)
> fix the drivers so that they can trust the core code not to trip them.
> 
> This small series, based on 5.17, addresses the above.

I have tested this patchset on D06. It works well with kernel parameter
'maxcpus=1' or 'nohz_full=1-127 isolcpus=nohz,domain,managed_irq,1-127'.
Also the 'effective_affinity' is correct. Thanks!
By the way, I merged the second patch manually because of conflicts.
Maybe I lack some patches on your local repo.

Thanks,
Xiongfeng

> 
> Thanks,
> 
> 	M.
> 
> [1] https://lore.kernel.org/r/78615d08-1764-c895-f3b7-bfddfbcbdfb9@huawei.com
> [2] https://lore.kernel.org/r/20220124073440.88598-1-wangxiongfeng2@huawei.com
> [3] https://lore.kernel.org/r/20220307190625.254426-1-maz@kernel.org
> 
> Marc Zyngier (3):
>   genirq/msi: Shutdown managed interrupts with unsatifiable affinities
>   genirq: Always limit the affinity to online CPUs
>   irqchip/gic-v3: Always trust the managed affinity provided by the core
>     code
> 
>  drivers/irqchip/irq-gic-v3-its.c |  2 +-
>  kernel/irq/manage.c              | 25 +++++++++++++++++--------
>  kernel/irq/msi.c                 | 15 +++++++++++++++
>  3 files changed, 33 insertions(+), 9 deletions(-)
> 

  parent reply	other threads:[~2022-03-23  3:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 19:36 Marc Zyngier
2022-03-21 19:36 ` [PATCH v2 1/3] genirq/msi: Shutdown managed interrupts with unsatifiable affinities Marc Zyngier
2022-03-21 19:36 ` [PATCH v2 2/3] genirq: Always limit the affinity to online CPUs Marc Zyngier
2022-03-21 19:36 ` [PATCH v2 3/3] irqchip/gic-v3: Always trust the managed affinity provided by the core code Marc Zyngier
2022-03-23  3:52 ` Xiongfeng Wang [this message]
2022-03-23  8:56   ` [PATCH v2 0/3] genirq: Managed affinity fixes Marc Zyngier
2022-03-23 10:58     ` Xiongfeng Wang
2022-03-23 11:31       ` Marc Zyngier

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=a83da394-dcc0-c9a6-1569-9c30fbc291fd@huawei.com \
    --to=wangxiongfeng2@huawei.com \
    --cc=ddecotig@google.com \
    --cc=john.garry@huawei.com \
    --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®