public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	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 08:56:40 +0000	[thread overview]
Message-ID: <87a6dhxd13.wl-maz@kernel.org> (raw)
In-Reply-To: <a83da394-dcc0-c9a6-1569-9c30fbc291fd@huawei.com>

Hi Xiongfeng,

On Wed, 23 Mar 2022 03:52:46 +0000,
Xiongfeng Wang <wangxiongfeng2@huawei.com> wrote:
> 
> 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!

Thanks for having given it a go.

> By the way, I merged the second patch manually because of conflicts.
> Maybe I lack some patches on your local repo.

That's odd, as the patches are directly sitting on top of 5.17 in my
tree (see [1]). Do you have any out of tree patches around? Please
make sure you test this without any extra change.

Thanks,

	M.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/managed-affinity-fixes

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2022-03-23  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 19:36 [PATCH v2 0/3] genirq: Managed affinity fixes 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 ` [PATCH v2 0/3] genirq: Managed affinity fixes Xiongfeng Wang
2022-03-23  8:56   ` Marc Zyngier [this message]
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=87a6dhxd13.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ddecotig@google.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangxiongfeng2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox