From: Bjorn Helgaas <helgaas@kernel.org>
To: Romain Bezut <rbezut@gmail.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH] PCI/MSI: Export all remapped MSIs to sysfs attributes
Date: Thu, 15 Oct 2015 12:23:05 -0500 [thread overview]
Message-ID: <20151015172305.GC17702@localhost> (raw)
In-Reply-To: <1443051076-27716-1-git-send-email-rbezut@gmail.com>
On Thu, Sep 24, 2015 at 01:31:16AM +0200, Romain Bezut wrote:
> irqbalance uses these attributes to populate its internal database, which is
> then used to bind the irq on the appropriate NUMA node.
>
> On a device accepting multiple MSIs and with interrupt remapping enabled,
> only the first irq entry is exported to msi_irqs directory.
> This results in irqbalance having no clue of the NUMA affinity for the extra
> irqs and starting to bind them on random nodes.
>
> This patch exports all MSI interrupts as sysfs attributes when relevant.
>
> Signed-off-by: Romain Bezut <rbezut@gmail.com>
Applied with Thomas' ack to pci/msi for v4.4, thanks, Romain!
> ---
> drivers/pci/msi.c | 31 +++++++++++++++++--------------
> 1 file changed, 17 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
> index d449714..324a164 100644
> --- a/drivers/pci/msi.c
> +++ b/drivers/pci/msi.c
> @@ -475,10 +475,11 @@ static int populate_msi_sysfs(struct pci_dev *pdev)
> int ret = -ENOMEM;
> int num_msi = 0;
> int count = 0;
> + int i;
>
> /* Determine how many msi entries we have */
> for_each_pci_msi_entry(entry, pdev)
> - ++num_msi;
> + num_msi += entry->nvec_used;
> if (!num_msi)
> return 0;
>
> @@ -487,19 +488,21 @@ static int populate_msi_sysfs(struct pci_dev *pdev)
> if (!msi_attrs)
> return -ENOMEM;
> for_each_pci_msi_entry(entry, pdev) {
> - msi_dev_attr = kzalloc(sizeof(*msi_dev_attr), GFP_KERNEL);
> - if (!msi_dev_attr)
> - goto error_attrs;
> - msi_attrs[count] = &msi_dev_attr->attr;
> -
> - sysfs_attr_init(&msi_dev_attr->attr);
> - msi_dev_attr->attr.name = kasprintf(GFP_KERNEL, "%d",
> - entry->irq);
> - if (!msi_dev_attr->attr.name)
> - goto error_attrs;
> - msi_dev_attr->attr.mode = S_IRUGO;
> - msi_dev_attr->show = msi_mode_show;
> - ++count;
> + for (i = 0; i < entry->nvec_used; i++) {
> + msi_dev_attr = kzalloc(sizeof(*msi_dev_attr), GFP_KERNEL);
> + if (!msi_dev_attr)
> + goto error_attrs;
> + msi_attrs[count] = &msi_dev_attr->attr;
> +
> + sysfs_attr_init(&msi_dev_attr->attr);
> + msi_dev_attr->attr.name = kasprintf(GFP_KERNEL, "%d",
> + entry->irq + i);
> + if (!msi_dev_attr->attr.name)
> + goto error_attrs;
> + msi_dev_attr->attr.mode = S_IRUGO;
> + msi_dev_attr->show = msi_mode_show;
> + ++count;
> + }
> }
>
> msi_irq_group = kzalloc(sizeof(*msi_irq_group), GFP_KERNEL);
> --
> 2.4.9
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-15 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 23:31 [PATCH] PCI/MSI: Export all remapped MSIs to sysfs attributes Romain Bezut
2015-10-09 22:33 ` Bjorn Helgaas
2015-10-11 9:49 ` Thomas Gleixner
2015-10-15 17:23 ` Bjorn Helgaas [this message]
2017-01-23 20:57 ` Myron Stowe
2017-01-23 21:49 ` Neil Horman
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=20151015172305.GC17702@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=rbezut@gmail.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;
as well as URLs for NNTP newsgroup(s).