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
| ||
|
Date: Fri, 1 May 2020 15:31:14 -0700 From: "Dey, Megha" <megha.dey@...ux.intel.com> To: Jason Gunthorpe <jgg@...lanox.com>, Dan Williams <dan.j.williams@...el.com> Cc: Dave Jiang <dave.jiang@...el.com>, Vinod Koul <vkoul@...nel.org>, maz@...nel.org, Bjorn Helgaas <bhelgaas@...gle.com>, "Rafael J. Wysocki" <rafael@...nel.org>, Greg KH <gregkh@...uxfoundation.org>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, Alex Williamson <alex.williamson@...hat.com>, Jacob jun Pan <jacob.jun.pan@...el.com>, "Raj, Ashok" <ashok.raj@...el.com>, Yi L Liu <yi.l.liu@...el.com>, Baolu Lu <baolu.lu@...el.com>, "Tian, Kevin" <kevin.tian@...el.com>, Sanjay K Kumar <sanjay.k.kumar@...el.com>, "Luck, Tony" <tony.luck@...el.com>, Jing Lin <jing.lin@...el.com>, kwankhede@...dia.com, eric.auger@...hat.com, parav@...lanox.com, dmaengine@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>, linux-pci@...r.kernel.org, KVM list <kvm@...r.kernel.org> Subject: Re: [PATCH RFC 00/15] Add VFIO mediated device support and IMS support for the idxd driver. Hi Jason, On 4/23/2020 12:49 PM, Jason Gunthorpe wrote: > On Thu, Apr 23, 2020 at 12:17:50PM -0700, Dan Williams wrote: > >> Per Megha's follow-up can you send the details about that other device >> and help clear a path for a device-specific MSI addr/data table >> format. Ever since HMM I've been sensitive, perhaps overly-sensitive, >> to claims about future upstream users. The fact that you have an >> additional use case is golden for pushing this into a common area and >> validating the scope of the proposed API. > > I think I said it at plumbers, but yes, we are interested in this, and > would like dynamic MSI-like interrupts available to the driver (what > Intel calls IMS) > So basically you are looking for a way to dynamically allocate the platform-msi interrupts, correct? Since I don't have access to any of the platform-msi devices, it is hard for me to test this code for other drivers expect idxd for now. Once I submit the next round of patches, after addressing all the comments, would it be possible for you to test this code for any of your devices? > It is something easy enough to illustrate with any RDMA device really, > just open a MR against the addr and use RDMA_WRITE to trigger the > data. It should trigger a Linux IRQ. Nothing else should be needed. > > Jason >
Powered by blists - more mailing lists