From: Chris Friesen <chris.friesen@windriver.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Nitesh Narayan Lal <nitesh@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [IRQ] IRQ affinity not working properly?
Date: Thu, 22 Apr 2021 11:00:59 -0600 [thread overview]
Message-ID: <c37ed332-6984-f0dc-35aa-1165a7218aac@windriver.com> (raw)
In-Reply-To: <87bla6xr59.ffs@nanos.tec.linutronix.de>
On 4/22/2021 9:42 AM, Thomas Gleixner wrote:
> On Wed, Apr 21 2021 at 09:31, Nitesh Narayan Lal wrote:
>> I agree it will be interesting to see with which kernel version Chris is
>> reproducing the issue.
>
> And the output of
>
> /proc/irq/$NUMBER/smp_affinity_list
> /proc/irq/$NUMBER/effective_affinity_list
I haven't forgotten about this, but I've had other priorities. Hoping
to get back to it in May sometime.
Chris
prev parent reply other threads:[~2021-04-22 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:17 [IRQ] IRQ affinity not working properly? Chris Friesen
2021-03-28 18:45 ` Thomas Gleixner
2021-04-21 13:31 ` Nitesh Narayan Lal
2021-04-22 15:42 ` Thomas Gleixner
2021-04-22 17:00 ` Chris Friesen [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=c37ed332-6984-f0dc-35aa-1165a7218aac@windriver.com \
--to=chris.friesen@windriver.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nitesh@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).