Hi Leon,
On 2/8/21 4:21 PM, Leon Romanovsky wrote:
On Wed, Feb 03, 2021 at 12:56:44PM -0800, Megha Dey wrote:
From: Lu Baolu
The pci_subdevice_msi_create_irq_domain() should fail if the underlying
platform is not able to support IMS (Interrupt Message Storage). Otherwise,
the isolation of int
On Wed, Feb 03, 2021 at 12:56:44PM -0800, Megha Dey wrote:
> From: Lu Baolu
>
> The pci_subdevice_msi_create_irq_domain() should fail if the underlying
> platform is not able to support IMS (Interrupt Message Storage). Otherwise,
> the isolation of interrupt is not guaranteed.
>
> For x86, IMS is
Hi Jason,
On 2021/2/4 20:14, Jason Gunthorpe wrote:
On Wed, Feb 03, 2021 at 12:56:44PM -0800, Megha Dey wrote:
+bool arch_support_pci_device_ims(struct pci_dev *pdev)
+{
Consistent language please, we are not using IMS elsewhere, this
feature is called device_msi in Linux.
Thanks for point
On Wed, Feb 03, 2021 at 12:56:44PM -0800, Megha Dey wrote:
> +bool arch_support_pci_device_ims(struct pci_dev *pdev)
> +{
Consistent language please, we are not using IMS elsewhere, this
feature is called device_msi in Linux.
Jason
From: Lu Baolu
The pci_subdevice_msi_create_irq_domain() should fail if the underlying
platform is not able to support IMS (Interrupt Message Storage). Otherwise,
the isolation of interrupt is not guaranteed.
For x86, IMS is only supported on bare metal for now. We could enable it
in the virtual
5 matches
Mail list logo
