linux-kernel - Why MSI is limited to 32 interrupts maximum

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <8520D5D51A55D047800579B0941471982594B0F3@XAP-PVEXMBX01.xlnx.xilinx.com>
Date:   Sat, 15 Oct 2016 12:37:55 +0000
From:   Bharat Kumar Gogada <bharat.kumar.gogada@...inx.com>
To:     "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     Bjorn Helgaas <helgaas@...nel.org>,
        "arnd@...db.de" <arnd@...db.de>,
        "Marc Zyngier" <marc.zyngier@....com>
Subject: Why MSI is limited to 32 interrupts maximum

Hi

Can anyone tell why MSI interrupts are limited to maximum 32 interrupts, even though we have 16bit message data register ?

Regards,
Bharat

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.