From: Yongji Xie <xyjxie@linux.vnet.ibm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
iommu@lists.linux-foundation.org, alex.williamson@redhat.com,
bhelgaas@google.com, aik@ozlabs.ru, benh@kernel.crashing.org,
paulus@samba.org, mpe@ellerman.id.au, joro@8bytes.org,
warrier@linux.vnet.ibm.com, zhong@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com, eric.auger@linaro.org,
will.deacon@arm.com, gwshan@linux.vnet.ibm.com,
David.Laight@ACULAB.COM, alistair@popple.id.au,
ruscur@russell.cc
Subject: Re: [PATCH 3/5] PCI: Set PCI_BUS_FLAGS_MSI_REMAP if MSI controller supports IRQ remapping
Date: Wed, 25 May 2016 13:48:00 +0800 [thread overview]
Message-ID: <201605250548.u4P5i1tA003562@mx0a-001b2d01.pphosted.com> (raw)
In-Reply-To: <20160524210434.GB16463@localhost>
On 2016/5/25 5:04, Bjorn Helgaas wrote:
> On Wed, Apr 27, 2016 at 08:43:28PM +0800, Yongji Xie wrote:
>> On ARM HW the capability of IRQ remapping is abstracted on
>> MSI controller side. MSI_FLAG_IRQ_REMAPPING is used to advertise
>> this [1].
>>
>> To have a universal flag to test this capability for different
>> archs on PCI side, we set PCI_BUS_FLAGS_MSI_REMAP for PCI buses
>> when MSI_FLAG_IRQ_REMAPPING is set.
>>
>> [1] http://www.spinics.net/lists/kvm/msg130256.html
>>
>> Signed-off-by: Yongji Xie <xyjxie@linux.vnet.ibm.com>
>> ---
>> drivers/pci/msi.c | 12 ++++++++++++
>> drivers/pci/probe.c | 3 +++
>> include/linux/msi.h | 6 +++++-
>> 3 files changed, 20 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
>> index a080f44..1661cdf 100644
>> --- a/drivers/pci/msi.c
>> +++ b/drivers/pci/msi.c
>> @@ -1134,6 +1134,18 @@ void *msi_desc_to_pci_sysdata(struct msi_desc *desc)
>> }
>> EXPORT_SYMBOL_GPL(msi_desc_to_pci_sysdata);
>>
>> +void pci_bus_check_msi_remapping(struct pci_bus *bus,
>> + struct irq_domain *domain)
>> +{
>> +#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN
>> + struct msi_domain_info *info;
>> +
>> + info = msi_get_domain_info(domain);
>> + if (info->flags & MSI_FLAG_IRQ_REMAPPING)
>> + bus->bus_flags |= PCI_BUS_FLAGS_MSI_REMAP;
>> +#endif
>> +}
> Functions named "check_foo" are a pet peeve of mine because the name
> doesn't tell us anything about what the function *does*. In this
> case, we know it checks something about MSI remapping, but we don't
> know whether we're checking whether it's enabled, disabled, or some
> other property.
>
> I'd prefer something like:
>
> int pci_bus_msi_isolated(struct pci_bus *bus, struct irq_domain *domain)
> {
> struct msi_domain_info *info;
>
> if (!domain)
> return 0;
>
> info = msi_get_domain_info(domain);
> if (info->flags & MSI_FLAG_IRQ_REMAPPING)
> return 1;
>
> return 0;
> }
>
> void pci_set_bus_msi_domain(struct pci_bus *bus)
> {
> ...
> if (b == bus && pci_bus_msi_isolated(bus, d))
> bus->bus_flags |= PCI_BUS_FLAGS_MSI_REMAP;
Yes. This looks more reasonable. Thank you!
Regards,
Yongji
next prev parent reply other threads:[~2016-05-25 5:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 12:43 [PATCH 0/5] vfio-pci: Add support for mmapping MSI-X table Yongji Xie
2016-04-27 12:43 ` [PATCH 1/5] PCI: Add a new PCI_BUS_FLAGS_MSI_REMAP flag Yongji Xie
2016-05-24 20:55 ` Bjorn Helgaas
2016-05-25 5:46 ` Yongji Xie
2016-04-27 12:43 ` [PATCH 2/5] iommu: Set PCI_BUS_FLAGS_MSI_REMAP if IOMMU have capability of IRQ remapping Yongji Xie
2016-05-24 21:11 ` Bjorn Helgaas
2016-05-25 5:54 ` Yongji Xie
[not found] ` <201605250554.u4P5sRqv014439@mx0a-001b2d01.pphosted.com>
2016-05-26 3:48 ` Bjorn Helgaas
2016-04-27 12:43 ` [PATCH 3/5] PCI: Set PCI_BUS_FLAGS_MSI_REMAP if MSI controller supports " Yongji Xie
2016-05-24 21:04 ` Bjorn Helgaas
2016-05-25 5:48 ` Yongji Xie [this message]
2016-04-27 12:43 ` [PATCH 4/5] pci-ioda: Set PCI_BUS_FLAGS_MSI_REMAP for IODA host bridge Yongji Xie
2016-05-06 6:34 ` Alexey Kardashevskiy
2016-04-27 12:43 ` [PATCH 5/5] vfio-pci: Allow to mmap MSI-X table if interrupt remapping is supported Yongji Xie
2016-05-03 5:34 ` Tian, Kevin
2016-05-03 6:08 ` Yongji Xie
2016-05-03 6:22 ` Tian, Kevin
2016-05-03 7:34 ` Yongji Xie
2016-05-05 9:36 ` Tian, Kevin
2016-05-05 9:54 ` David Laight
2016-05-05 11:42 ` Yongji Xie
2016-05-05 12:15 ` Tian, Kevin
2016-05-05 13:28 ` Yongji Xie
2016-05-05 15:05 ` Alex Williamson
2016-05-06 6:35 ` Alexey Kardashevskiy
2016-05-06 16:54 ` Alex Williamson
2016-05-11 6:29 ` Tian, Kevin
2016-05-11 15:53 ` Alex Williamson
2016-05-12 1:19 ` Tian, Kevin
2016-05-12 2:20 ` Alex Williamson
2016-05-12 4:53 ` Tian, Kevin
2016-05-12 17:47 ` Alex Williamson
2016-05-13 2:33 ` Tian, Kevin
2016-05-13 5:32 ` Alex Williamson
2016-05-13 6:50 ` Tian, Kevin
2016-05-13 16:42 ` Alex Williamson
2016-05-13 9:16 ` David Laight
2016-05-13 2:36 ` Tian, Kevin
2016-05-05 11:44 ` Yongji Xie
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=201605250548.u4P5i1tA003562@mx0a-001b2d01.pphosted.com \
--to=xyjxie@linux.vnet.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=eric.auger@linaro.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=ruscur@russell.cc \
--cc=warrier@linux.vnet.ibm.com \
--cc=will.deacon@arm.com \
--cc=zhong@linux.vnet.ibm.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).