Thread (65 messages) 65 messages, 5 authors, 2014-11-06

[Patch Part2 v4 21/31] PCI/MSI: enhance PCI MSI core to support hierarchy irqdomain

From: Yijing Wang <hidden>
Date: 2014-11-06 04:55:28
Also in: linux-acpi, linux-pci, lkml

On 2014/11/6 12:10, Bjorn Helgaas wrote:
On Wed, Nov 5, 2014 at 6:58 PM, Yijing Wang [off-list ref] wrote:
quoted
quoted
quoted
+{
+    return (irq_hw_number_t)msidesc->msi_attrib.entry_nr |
+            PCI_DEVID(pdev->bus->number, pdev->devfn) << 11 |
+            (pci_domain_nr(pdev->bus) & 0xFFFFFFFF) << 27;
Where does this bit layout come from?  Is this defined in the spec
somewhere?  A reference would help.
Currently, more and more Non-PCI device use MSI(or similar MSI mechanism), like DMAR fault irq
and HPET FSB irq. And we have to add additional code to support the MSI capability.
So I hope we can decouple MSI code and PCI code, then we can unify all MSI(or Message Based interrupt)
in one framework.
Was that supposed to answer my question?  If so, I didn't understand
how it explains where the bit layout came from.
No, that's just my concern. Because this function uses the pci device id,
but more and more Non-PCI devices use MSI.
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

.

-- 
Thanks!
Yijing
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help