linux-kernel - Re: [PATCH] usb: enable pci MSI/MSIX in usb core

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120207144204.GA7214@kroah.com>
Date:	Tue, 7 Feb 2012 06:42:04 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Alex Shi <alex.shi@...el.com>
Cc:	sarah.a.sharp@...ux.intel.com, stern@...land.harvard.edu,
	linux-usb@...r.kernel.org, andiry.xu@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: enable pci MSI/MSIX in usb core

On Tue, Feb 07, 2012 at 07:59:47PM +0800, Alex Shi wrote:
> On 02/06/2012 08:29 PM, Alex Shi wrote:
> 
> > MSI/MSIX is the favorite interrupt for PCIe device. PCIe usb HCD should
> > be used more and more in future, but current USB core still just wants
> > line IRQ, only XHCI usb driver enabled MSI/MSIX.
> > 
> > This patch enabled pci MSI/MSIX in usb core for HCD, and removed MSI/MSIX
> > setup code from XHCI since it becomes redundant now.
> > There 2 places need prepare to enable MSI/MSIX in usb driver.
> > 1, set HCD_MSI_FIRST in driver->flags to enable MSI/MSIX.
> > 2, prepare a get_msix_num() for specific drivers.
> > XHCI is a good example for this.
> > 
> > This patch bases on my "USB-try-MSI-before-legacy-irq-on-pci-xhci-HCD"
> > patch.
> 
> 
> Gregkh&Alan:
> 
> Do you need a full patch that include my recent MSI setup/bug fix
> patches? or just this one is ok?

I was thinking that Sarah would forward this on.  We need whatever
should be applied to the tree, as I do not have any pending patches from
you in my queue.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/