[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YRT/uGklgx2Wmd5v@kroah.com>
Date: Thu, 12 Aug 2021 13:02:16 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Barry Song <21cnbao@...il.com>
Cc: rafael@...nel.org, bhelgaas@...gle.com, maz@...nel.org,
tglx@...utronix.de, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, linuxarm@...wei.com,
robin.murphy@....com, will@...nel.org, lorenzo.pieralisi@....com,
dwmw@...zon.co.uk, Barry Song <song.bao.hua@...ilicon.com>
Subject: Re: [PATCH v2 0/2] msi: extend msi_irqs sysfs entries to platform
devices
On Thu, Aug 12, 2021 at 10:53:39PM +1200, Barry Song wrote:
> From: Barry Song <song.bao.hua@...ilicon.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.
Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Powered by blists - more mailing lists