mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@misterjones.org>
To: Thomas Gleixner <tglx@linutronix.de>, Yunfeng Ye <yeyunfeng@huawei.com>
Cc: Shiyuan Hu <hushiyuan@huawei.com>,
	Hewenliang <hewenliang4@huawei.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/affinity: show managed irq affinity correctly
Date: Sat, 15 Aug 2020 15:29:41 +0100	[thread overview]
Message-ID: <11bb7a215cd8757f298d9f9608ed125c@misterjones.org> (raw)
In-Reply-To: <877du355o1.fsf@nanos.tec.linutronix.de>

On 2020-08-13 09:08, Thomas Gleixner wrote:
> Yunfeng Ye <yeyunfeng@huawei.com> writes:

[...]

> You are looking at the wrong file. /proc/irq/$IRQ/smp_affinity* is the
> possible mask. If you want to know to which CPU an interrupt is affine
> then look at /proc/irq/$IRQ/effective_affinity*
> 
> If effective_affinity* is not showing the correct value, then the irq
> chip affinity setter is broken and needs to be fixed.

In order to reassure myself that nothing was untoward in GIC-land,
I went in and looked at an ITS-based VM running whatever is in
Linus' tree today. I see the effective affinity being correctly
setup, and being as expected a subset of the affinity. This is
without isolcpu though.

In any case, I'd be interested in understanding what this patch is
trying to solve, really.

         M.
-- 
Who you jivin' with that Cosmik Debris?

      reply	other threads:[~2020-08-15 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  6:17 Yunfeng Ye
2020-08-13  8:08 ` Thomas Gleixner
2020-08-15 14:29   ` Marc Zyngier [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=11bb7a215cd8757f298d9f9608ed125c@misterjones.org \
    --to=maz@misterjones.org \
    --cc=hewenliang4@huawei.com \
    --cc=hushiyuan@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yeyunfeng@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

all inboxes | Powered by JetHome®