From: Marc Zyngier <maz@kernel.org>
To: Barry Song <21cnbao@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
bhelgaas@google.com, dwmw@amazon.co.uk,
gregkh@linuxfoundation.org, linux-pci@vger.kernel.org,
linuxarm@huawei.com, lorenzo.pieralisi@arm.com,
rafael@kernel.org, robin.murphy@arm.com,
song.bao.hua@hisilicon.com, will@kernel.org
Subject: Re: [PATCH v3 0/2] msi: extend msi_irqs sysfs entries to platform devices
Date: Sat, 14 Aug 2021 10:45:19 +0100 [thread overview]
Message-ID: <87fsvc1hsg.wl-maz@kernel.org> (raw)
In-Reply-To: <20210813035628.6844-1-21cnbao@gmail.com>
On Fri, 13 Aug 2021 04:56:26 +0100,
Barry Song <21cnbao@gmail.com> wrote:
>
> From: Barry Song <song.bao.hua@hisilicon.com>
>
> -v3:
> added Acked-by of Greg Kroah-Hartman and Bjorn Helgaas, thanks!
> refined commit log with respect to Bjorn's comments
>
> Hi Thomas & Marc,
> Would you please handle this series? Thanks!
>
> -v2:
> extract common code for msi_irqs sysfs populate/destory from PCI to MSI core,
> platform_device can directly reuse common code;
> https://lore.kernel.org/lkml/20210812105341.51657-1-21cnbao@gmail.com/
>
> -v1:
> https://lore.kernel.org/lkml/20210811105020.12980-1-song.bao.hua@hisilicon.com/
>
> Just like pci devices have msi_irqs which can be used by userspace irq affinity
> tools or applications to bind irqs, platform devices also widely support msi
> irqs.
> For platform devices, for example ARM SMMU, userspaces also care about its msi
> irqs as applications can know the mapping between devices and irqs and then
> make smarter decision on handling irq affinity. For example, for SVA mode,
> it is better to pin io page fault to the numa node applications are running
> on. Otherwise, io page fault will get a remote page from the node iopf happens
> rather than from the node applications are running on.
>
> The first patch extracts the sysfs populate/destory code from PCI to
> MSI core. The 2nd patch lets platform-msi export msi_irqs entry so that
> userspace can know the mapping between devices and irqs for platform
> devices.
Although I'm not in a position to test it right now, this looks
reasonable to me:
Acked-by: Marc Zyngier <maz@kernel.org>
Thomas, do you want to queue this one, given that you already carry a
ton of MSI-related patches?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-08-14 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 3:56 [PATCH v3 0/2] msi: extend msi_irqs sysfs entries to platform devices Barry Song
2021-08-13 3:56 ` [PATCH v3 1/2] genirq/msi: Extract common sysfs populate entries to MSI core from PCI Barry Song
2021-08-13 3:56 ` [PATCH v3 2/2] platform-msi: Add ABI to show msi_irqs of platform devices Barry Song
2021-08-14 9:45 ` 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=87fsvc1hsg.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=21cnbao@gmail.com \
--cc=bhelgaas@google.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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).