Re: [Xen-devel] [PATCH v1 08/21] x86/xen/MSI: Use MSI chip framework to configure MSI/MSI-X irq
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: David Vrabel <david.vrabel@xxxxxxxxxx>, Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
- Subject: Re: [Xen-devel] [PATCH v1 08/21] x86/xen/MSI: Use MSI chip framework to configure MSI/MSI-X irq
- From: Yijing Wang <wangyijing@xxxxxxxxxx>
- Date: Thu, 11 Sep 2014 09:27:10 +0800
- Cc: <linux-mips@xxxxxxxxxxxxxx>, <linux-ia64@xxxxxxxxxxxxxxx>, <linux-pci@xxxxxxxxxxxxxxx>, Xinwei Hu <huxinwei@xxxxxxxxxx>, <sparclinux@xxxxxxxxxxxxxxx>, <linux-arch@xxxxxxxxxxxxxxx>, <linux-s390@xxxxxxxxxxxxxxx>, Russell King <linux@xxxxxxxxxxxxxxxx>, "Joerg Roedel" <joro@xxxxxxxxxx>, <x86@xxxxxxxxxx>, Sebastian Ott <sebott@xxxxxxxxxxxxxxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>, <arnab.basu@xxxxxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Chris Metcalf <cmetcalf@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, <Bharat.Bhushan@xxxxxxxxxxxxx>, "Tony Luck" <tony.luck@xxxxxxxxx>, Ralf Baechle <ralf@xxxxxxxxxxxxxx>, <iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx>, Wuyun <wuyun.wu@xxxxxxxxxx>, <linuxppc-dev@xxxxxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>
- In-reply-to: <54104641.7020007@citrix.com>
- List-id: <linux-ia64.vger.kernel.org>
- References: <1409911806-10519-1-git-send-email-wangyijing@huawei.com> <1409911806-10519-9-git-send-email-wangyijing@huawei.com> <5409C8C0.8020200@citrix.com> <540E6095.8030409@huawei.com> <54104641.7020007@citrix.com>
- User-agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
On 2014/9/10 20:38, David Vrabel wrote:
> On 09/09/14 03:06, Yijing Wang wrote:
>> On 2014/9/5 22:29, David Vrabel wrote:
>>> On 05/09/14 11:09, Yijing Wang wrote:
>>>> Use MSI chip framework instead of arch MSI functions to configure
>>>> MSI/MSI-X irq. So we can manage MSI/MSI-X irq in a unified framework.
>>> [...]
>>>> --- a/arch/x86/pci/xen.c
>>>> +++ b/arch/x86/pci/xen.c
>>> [...]
>>>> @@ -418,9 +430,9 @@ int __init pci_xen_init(void)
>>>> #endif
>>>>
>>>> #ifdef CONFIG_PCI_MSI
>>>> - x86_msi.setup_msi_irqs = xen_setup_msi_irqs;
>>>> - x86_msi.teardown_msi_irq = xen_teardown_msi_irq;
>>>> - x86_msi.teardown_msi_irqs = xen_teardown_msi_irqs;
>>>> + xen_msi_chip.setup_irqs = xen_setup_msi_irqs;
>>>> + xen_msi_chip.teardown_irqs = xen_teardown_msi_irqs;
>>>> + x86_msi_chip = &xen_msi_chip;
>>>> msi_chip.irq_mask = xen_nop_msi_mask;
>>>> msi_chip.irq_unmask = xen_nop_msi_mask;
>>>
>>> Why have these not been changed to set the x86_msi_chip.mask/unmask
>>> fields instead?
>>
>> Hi David, x86_msi_chip here is struct msi_chip data type, used to configure MSI/MSI-X
>> irq. msi_chip above is struct irq_chip data type, represent the MSI irq controller. They are
>> not the same object. Their name easily confusing people.
>
> Ok, it all makes sense now.
>
> Acked-by: David Vrabel <david.vrabel@xxxxxxxxxx>
Thanks!
>
> David
>
> .
>
--
Thanks!
Yijing
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]