public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tsai Sung-Fu <danielsftsai@google.com>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Andrew Chant" <achant@google.com>,
	"Brian Norris" <briannorris@google.com>,
	"Sajid Dalvi" <sdalvi@google.com>,
	"Mark Cheng" <markcheng@google.com>,
	"Ben Cheng" <bccheng@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Marc Zyngier" <maz@kernel.org>
Subject: Re: [PATCH] PCI: dwc: Chain the set IRQ affinity request back to the parent
Date: Tue, 11 Mar 2025 15:05:17 +0100	[thread overview]
Message-ID: <874izz1x42.ffs@tglx> (raw)
In-Reply-To: <CAK7fddBSJk61h2t73Ly9gxNX22cGAF46kAP+A2T5BU8VKENceQ@mail.gmail.com>

On Tue, Mar 11 2025 at 17:52, Tsai Sung-Fu wrote:

Please do not top-post and trim your replies.

> Running some basic tests with this patch (
> https://tglx.de/~tglx/patches.tar ) applied on my device, at first
> glance, the affinity feature is working.
>
> I didn't run stress test to test the stability, and the Kernel version
> we used is a bit old, so I only applied change in this 2 patches

I don't care about old kernels and what you can apply or not. Kernel
development happens against upstream and not against randomly chosen
private kernel versions.

> And adding if check on irq_chip_redirect_set_affinity() and
> irq_set_redirect_target() to avoid cpumask_first() return nr_cpu_ids

I assume you know how diff works.

> May I ask, would this patch be officially added to the 6.14 kernel ?

You may ask. But you should know the answer already, no?

The merge window for 6.14 closed on February 2nd with the release of
6.14-rc1. Anything which goes into Linus tree between rc1 and the final
release is fixes only.

This is new infrastructure, which has neither been posted nor reviewed
nor properly tested. There are also no numbers about the overhead and
no analysis whether that overhead causes regressions on existing setups.

These changes want to be:

   1) Put into a series with proper change logs

   2) Posted on the relevant mailing list

   3) Tested and proper numbers provided

So they are not even close to be ready for the 6.15 merge window, simply
because the irq tree is going to freeze at 6.14-rc7, i.e. by the end of
this week.

I'm not planning to work on them. Feel free to take the PoC patches,
polish them up and post them according to the documented process.

Thanks,

        tglx

  reply	other threads:[~2025-03-11 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  7:05 [PATCH] PCI: dwc: Chain the set IRQ affinity request back to the parent Daniel Tsai
2025-03-03  9:10 ` Thomas Gleixner
2025-03-04  5:48   ` Tsai Sung-Fu
2025-03-04  9:46     ` Thomas Gleixner
2025-03-05 11:21       ` Tsai Sung-Fu
2025-03-06  7:44         ` Thomas Gleixner
2025-03-07 11:10           ` Tsai Sung-Fu
2025-03-07 19:49             ` Thomas Gleixner
2025-03-11  9:52               ` Tsai Sung-Fu
2025-03-11 14:05                 ` Thomas Gleixner [this message]
2025-03-25  6:38                   ` Tsai Sung-Fu
2025-05-07 11:10                     ` Krishna Chaitanya Chundru
2025-03-03  9:25 ` kernel test robot
2025-03-03 10:13 ` kernel test robot

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=874izz1x42.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=achant@google.com \
    --cc=bccheng@google.com \
    --cc=bhelgaas@google.com \
    --cc=briannorris@google.com \
    --cc=danielsftsai@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=markcheng@google.com \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=sdalvi@google.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