From: Greg KH <gregkh@linuxfoundation.org>
To: raoxu <raoxu@uniontech.com>
Cc: mathias.nyman@linux.intel.com, linux-usb@vger.kernel.org,
michal.pecio@gmail.com, niklas.neronin@linux.intel.com,
zhanjun@uniontech.com
Subject: Re: [PATCH v2] usb: xhci: route endpoints to secondary interrupters
Date: Wed, 17 Dec 2025 10:24:42 +0100 [thread overview]
Message-ID: <2025121728-linguini-denote-8568@gregkh> (raw)
In-Reply-To: <7D02195CD578C798+20251217085407.3774968-1-raoxu@uniontech.com>
On Wed, Dec 17, 2025 at 04:54:07PM +0800, raoxu wrote:
> This demonstrates that transfer completions are no longer handled
> exclusively by interrupter 0, but are instead distributed across
> multiple MSI-X vectors.
>
> Signed-off-by: Xu Rao <raoxu@uniontech.com>
>
> Changelog:
> v1 -> v2:
> - Bind interrupters to endpoints at enable time instead of selecting
> per transfer.
> - Store the selected interrupter in struct xhci_virt_ep and program
> TRB_INTR_TARGET() from the bound interrupter.
> - Use a single IRQ handler for both primary and secondary vectors,
> with STS_EINT handling restricted to interrupter 0.
> - Keep a common dev_id for IRQ registration to match the existing
> xhci_cleanup_msix() teardown constraints and avoid dev_id
> lifetime issues.
> - Clarify secondary interrupter teardown to avoid double-free or
> use-after-free during xHCI removal.
> ---
> drivers/usb/host/xhci-mem.c | 86 +++++++++++++++++++++++++++++++++---
> drivers/usb/host/xhci-pci.c | 28 ++++++++++++
> drivers/usb/host/xhci-ring.c | 79 ++++++++++++++++++++++++---------
> drivers/usb/host/xhci.c | 38 ++++++++++++++++
> drivers/usb/host/xhci.h | 7 +++
> 5 files changed, 212 insertions(+), 26 deletions(-)
Changelog goes below the --- line please.
thanks,
greg k-h
prev parent reply other threads:[~2025-12-17 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 8:54 [PATCH v2] usb: xhci: route endpoints to secondary interrupters raoxu
2025-12-17 9:24 ` Greg KH [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=2025121728-linguini-denote-8568@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@gmail.com \
--cc=niklas.neronin@linux.intel.com \
--cc=raoxu@uniontech.com \
--cc=zhanjun@uniontech.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