2020-09-15 23:34:40

by Dave Jiang

[permalink] [raw]
Subject: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support

From: Megha Dey <[email protected]>

Add required support in the interrupt remapping driver for devices
which generate dev-msi interrupts and use the intel remapping
domain as the parent domain.

Signed-off-by: Megha Dey <[email protected]>
Signed-off-by: Dave Jiang <[email protected]>
Reviewed-by: Ashok Raj <[email protected]>
---
drivers/iommu/intel/irq_remapping.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
index 0cfce1d3b7bb..75e388263b78 100644
--- a/drivers/iommu/intel/irq_remapping.c
+++ b/drivers/iommu/intel/irq_remapping.c
@@ -1303,9 +1303,10 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
case X86_IRQ_ALLOC_TYPE_HPET:
case X86_IRQ_ALLOC_TYPE_PCI_MSI:
case X86_IRQ_ALLOC_TYPE_PCI_MSIX:
+ case X86_IRQ_ALLOC_TYPE_DEV_MSI:
if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
set_hpet_sid(irte, info->devid);
- else
+ else if (info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
set_msi_sid(irte, msi_desc_to_pci_dev(info->desc));

msg->address_hi = MSI_ADDR_BASE_HI;
@@ -1358,7 +1359,8 @@ static int intel_irq_remapping_alloc(struct irq_domain *domain,
if (!info || !iommu)
return -EINVAL;
if (nr_irqs > 1 && info->type != X86_IRQ_ALLOC_TYPE_PCI_MSI &&
- info->type != X86_IRQ_ALLOC_TYPE_PCI_MSIX)
+ info->type != X86_IRQ_ALLOC_TYPE_PCI_MSIX &&
+ info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
return -EINVAL;

/*


2020-09-30 18:35:42

by Thomas Gleixner

[permalink] [raw]
Subject: Re: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support

On Tue, Sep 15 2020 at 16:27, Dave Jiang wrote:
> @@ -1303,9 +1303,10 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> case X86_IRQ_ALLOC_TYPE_HPET:
> case X86_IRQ_ALLOC_TYPE_PCI_MSI:
> case X86_IRQ_ALLOC_TYPE_PCI_MSIX:
> + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> set_hpet_sid(irte, info->devid);
> - else
> + else if (info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
> set_msi_sid(irte,
> msi_desc_to_pci_dev(info->desc));

Gah. this starts to become unreadable.

diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
index 8f4ce72570ce..0c1ea8ceec31 100644
--- a/drivers/iommu/intel/irq_remapping.c
+++ b/drivers/iommu/intel/irq_remapping.c
@@ -1271,6 +1271,16 @@ static struct irq_chip intel_ir_chip = {
.irq_set_vcpu_affinity = intel_ir_set_vcpu_affinity,
};

+static void irte_prepare_msg(struct msi_msg *msg, int index, int subhandle)
+{
+ msg->address_hi = MSI_ADDR_BASE_HI;
+ msg->data = sub_handle;
+ msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
+ MSI_ADDR_IR_SHV |
+ MSI_ADDR_IR_INDEX1(index) |
+ MSI_ADDR_IR_INDEX2(index);
+}
+
static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
struct irq_cfg *irq_cfg,
struct irq_alloc_info *info,
@@ -1312,19 +1322,18 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
break;

case X86_IRQ_ALLOC_TYPE_HPET:
+ set_hpet_sid(irte, info->hpet_id);
+ irte_prepare_msg(msg, index, sub_handle);
+ break;
+
case X86_IRQ_ALLOC_TYPE_MSI:
case X86_IRQ_ALLOC_TYPE_MSIX:
- if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
- set_hpet_sid(irte, info->hpet_id);
- else
- set_msi_sid(irte, info->msi_dev);
-
- msg->address_hi = MSI_ADDR_BASE_HI;
- msg->data = sub_handle;
- msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
- MSI_ADDR_IR_SHV |
- MSI_ADDR_IR_INDEX1(index) |
- MSI_ADDR_IR_INDEX2(index);
+ set_msi_sid(irte, info->msi_dev);
+ irte_prepare_msg(msg, index, sub_handle);
+ break;
+
+ case X86_IRQ_ALLOC_TYPE_DEV_MSI:
+ irte_prepare_msg(msg, index, sub_handle);
break;

default:

Hmm?

Thanks,

tglx

2020-10-01 23:27:45

by Megha Dey

[permalink] [raw]
Subject: Re: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support

Hi Thomas,

On 9/30/2020 11:32 AM, Thomas Gleixner wrote:
> On Tue, Sep 15 2020 at 16:27, Dave Jiang wrote:
>> @@ -1303,9 +1303,10 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
>> case X86_IRQ_ALLOC_TYPE_HPET:
>> case X86_IRQ_ALLOC_TYPE_PCI_MSI:
>> case X86_IRQ_ALLOC_TYPE_PCI_MSIX:
>> + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
>> if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
>> set_hpet_sid(irte, info->devid);
>> - else
>> + else if (info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
>> set_msi_sid(irte,
>> msi_desc_to_pci_dev(info->desc));
> Gah. this starts to become unreadable.
hmm ok will change it.
>
> diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
> index 8f4ce72570ce..0c1ea8ceec31 100644
> --- a/drivers/iommu/intel/irq_remapping.c
> +++ b/drivers/iommu/intel/irq_remapping.c
> @@ -1271,6 +1271,16 @@ static struct irq_chip intel_ir_chip = {
> .irq_set_vcpu_affinity = intel_ir_set_vcpu_affinity,
> };
>
> +static void irte_prepare_msg(struct msi_msg *msg, int index, int subhandle)
> +{
> + msg->address_hi = MSI_ADDR_BASE_HI;
> + msg->data = sub_handle;
> + msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
> + MSI_ADDR_IR_SHV |
> + MSI_ADDR_IR_INDEX1(index) |
> + MSI_ADDR_IR_INDEX2(index);
> +}
> +
> static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> struct irq_cfg *irq_cfg,
> struct irq_alloc_info *info,
> @@ -1312,19 +1322,18 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> break;
>
> case X86_IRQ_ALLOC_TYPE_HPET:
> + set_hpet_sid(irte, info->hpet_id);
> + irte_prepare_msg(msg, index, sub_handle);
> + break;
> +
> case X86_IRQ_ALLOC_TYPE_MSI:
> case X86_IRQ_ALLOC_TYPE_MSIX:
> - if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> - set_hpet_sid(irte, info->hpet_id);
> - else
> - set_msi_sid(irte, info->msi_dev);
> -
> - msg->address_hi = MSI_ADDR_BASE_HI;
> - msg->data = sub_handle;
> - msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
> - MSI_ADDR_IR_SHV |
> - MSI_ADDR_IR_INDEX1(index) |
> - MSI_ADDR_IR_INDEX2(index);
> + set_msi_sid(irte, info->msi_dev);
> + irte_prepare_msg(msg, index, sub_handle);
> + break;
> +
> + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> + irte_prepare_msg(msg, index, sub_handle);
> break;
>
> default:
>
> Hmm?

ok so I have no clue what happened here. This was the patch that was
sent out:

https://lore.kernel.org/lkml/160021246905.67751.1674517279122764758.stgit@djiang5-desk3.ch.intel.com/

and this does not have the above change. Not sure what happened here.

Anyways, this should not be there.

>
> Thanks,
>
> tglx

2020-10-02 11:14:40

by Thomas Gleixner

[permalink] [raw]
Subject: Re: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support

On Thu, Oct 01 2020 at 16:26, Megha Dey wrote:
> On 9/30/2020 11:32 AM, Thomas Gleixner wrote:
>> diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
>> index 8f4ce72570ce..0c1ea8ceec31 100644
>> --- a/drivers/iommu/intel/irq_remapping.c
>> +++ b/drivers/iommu/intel/irq_remapping.c
>> @@ -1271,6 +1271,16 @@ static struct irq_chip intel_ir_chip = {
>> .irq_set_vcpu_affinity = intel_ir_set_vcpu_affinity,
>> };
>>
>> +static void irte_prepare_msg(struct msi_msg *msg, int index, int subhandle)
>> +{
>> + msg->address_hi = MSI_ADDR_BASE_HI;
>> + msg->data = sub_handle;
>> + msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
>> + MSI_ADDR_IR_SHV |
>> + MSI_ADDR_IR_INDEX1(index) |
>> + MSI_ADDR_IR_INDEX2(index);
>> +}
>> +
>> static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
>> struct irq_cfg *irq_cfg,
>> struct irq_alloc_info *info,
>> @@ -1312,19 +1322,18 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
>> break;
>>
>> case X86_IRQ_ALLOC_TYPE_HPET:
>> + set_hpet_sid(irte, info->hpet_id);
>> + irte_prepare_msg(msg, index, sub_handle);
>> + break;
>> +
>> case X86_IRQ_ALLOC_TYPE_MSI:
>> case X86_IRQ_ALLOC_TYPE_MSIX:
>> - if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
>> - set_hpet_sid(irte, info->hpet_id);
>> - else
>> - set_msi_sid(irte, info->msi_dev);
>> -
>> - msg->address_hi = MSI_ADDR_BASE_HI;
>> - msg->data = sub_handle;
>> - msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
>> - MSI_ADDR_IR_SHV |
>> - MSI_ADDR_IR_INDEX1(index) |
>> - MSI_ADDR_IR_INDEX2(index);
>> + set_msi_sid(irte, info->msi_dev);
>> + irte_prepare_msg(msg, index, sub_handle);
>> + break;
>> +
>> + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
>> + irte_prepare_msg(msg, index, sub_handle);
>> break;
>>
>> default:
>>
>> Hmm?
>
> ok so I have no clue what happened here. This was the patch that was
> sent out:
> and this does not have the above change. Not sure what happened here.

Of course it was not there. I added this in my reply obviously for
illustration. It's not '> ' quoted, right?

Thanks,

tglx

2020-10-08 07:59:10

by David Woodhouse

[permalink] [raw]
Subject: Re: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support

On Wed, 2020-09-30 at 20:32 +0200, Thomas Gleixner wrote:
> On Tue, Sep 15 2020 at 16:27, Dave Jiang wrote:
> > @@ -1303,9 +1303,10 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> > case X86_IRQ_ALLOC_TYPE_HPET:
> > case X86_IRQ_ALLOC_TYPE_PCI_MSI:
> > case X86_IRQ_ALLOC_TYPE_PCI_MSIX:
> > + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> > if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> > set_hpet_sid(irte, info->devid);
> > - else
> > + else if (info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
> > set_msi_sid(irte,
> > msi_desc_to_pci_dev(info->desc));
>
> Gah. this starts to become unreadable.
>
> diff --git a/drivers/iommu/intel/irq_remapping.c b/drivers/iommu/intel/irq_remapping.c
> index 8f4ce72570ce..0c1ea8ceec31 100644
> --- a/drivers/iommu/intel/irq_remapping.c
> +++ b/drivers/iommu/intel/irq_remapping.c
> @@ -1271,6 +1271,16 @@ static struct irq_chip intel_ir_chip = {
> .irq_set_vcpu_affinity = intel_ir_set_vcpu_affinity,
> };
>
> +static void irte_prepare_msg(struct msi_msg *msg, int index, int subhandle)
> +{
> + msg->address_hi = MSI_ADDR_BASE_HI;
> + msg->data = sub_handle;
> + msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
> + MSI_ADDR_IR_SHV |
> + MSI_ADDR_IR_INDEX1(index) |
> + MSI_ADDR_IR_INDEX2(index);
> +}
> +
> static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> struct irq_cfg *irq_cfg,
> struct irq_alloc_info *info,
> @@ -1312,19 +1322,18 @@ static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> break;
>
> case X86_IRQ_ALLOC_TYPE_HPET:
> + set_hpet_sid(irte, info->hpet_id);
> + irte_prepare_msg(msg, index, sub_handle);
> + break;
> +
> case X86_IRQ_ALLOC_TYPE_MSI:
> case X86_IRQ_ALLOC_TYPE_MSIX:
> - if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> - set_hpet_sid(irte, info->hpet_id);
> - else
> - set_msi_sid(irte, info->msi_dev);
> -
> - msg->address_hi = MSI_ADDR_BASE_HI;
> - msg->data = sub_handle;
> - msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
> - MSI_ADDR_IR_SHV |
> - MSI_ADDR_IR_INDEX1(index) |
> - MSI_ADDR_IR_INDEX2(index);
> + set_msi_sid(irte, info->msi_dev);
> + irte_prepare_msg(msg, index, sub_handle);
> + break;
> +
> + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> + irte_prepare_msg(msg, index, sub_handle);
> break;
>
> default:
>
> Hmm?

It'd get a bit nicer if you *always* did the irte_prepare_msg() part to
generate the MSI message. Let the IOAPIC driver swizzle that into the
IOAPIC RTE for itself. You have no business composing an IOAPIC RTE
here.

Then your switch statement is *only* for setting the SID in the IRTE
appropriately.


Attachments:
smime.p7s (5.05 kB)

2020-10-21 19:43:50

by Megha Dey

[permalink] [raw]
Subject: RE: [PATCH v3 02/18] iommu/vt-d: Add DEV-MSI support



Hi David,

> On Wed, 2020-09-30 at 20:32 +0200, Thomas Gleixner wrote:
> > On Tue, Sep 15 2020 at 16:27, Dave Jiang wrote:
> > > @@ -1303,9 +1303,10 @@ static void
> intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> > > case X86_IRQ_ALLOC_TYPE_HPET:
> > > case X86_IRQ_ALLOC_TYPE_PCI_MSI:
> > > case X86_IRQ_ALLOC_TYPE_PCI_MSIX:
> > > + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> > > if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> > > set_hpet_sid(irte, info->devid);
> > > - else
> > > + else if (info->type != X86_IRQ_ALLOC_TYPE_DEV_MSI)
> > > set_msi_sid(irte,
> > > msi_desc_to_pci_dev(info->desc));
> >
> > Gah. this starts to become unreadable.
> >
> > diff --git a/drivers/iommu/intel/irq_remapping.c
> b/drivers/iommu/intel/irq_remapping.c
> > index 8f4ce72570ce..0c1ea8ceec31 100644
> > --- a/drivers/iommu/intel/irq_remapping.c
> > +++ b/drivers/iommu/intel/irq_remapping.c
> > @@ -1271,6 +1271,16 @@ static struct irq_chip intel_ir_chip = {
> > .irq_set_vcpu_affinity = intel_ir_set_vcpu_affinity,
> > };
> >
> > +static void irte_prepare_msg(struct msi_msg *msg, int index, int subhandle)
> > +{
> > + msg->address_hi = MSI_ADDR_BASE_HI;
> > + msg->data = sub_handle;
> > + msg->address_lo = MSI_ADDR_BASE_LO | MSI_ADDR_IR_EXT_INT |
> > + MSI_ADDR_IR_SHV |
> > + MSI_ADDR_IR_INDEX1(index) |
> > + MSI_ADDR_IR_INDEX2(index);
> > +}
> > +
> > static void intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> > struct irq_cfg *irq_cfg,
> > struct irq_alloc_info *info,
> > @@ -1312,19 +1322,18 @@ static void
> intel_irq_remapping_prepare_irte(struct intel_ir_data *data,
> > break;
> >
> > case X86_IRQ_ALLOC_TYPE_HPET:
> > + set_hpet_sid(irte, info->hpet_id);
> > + irte_prepare_msg(msg, index, sub_handle);
> > + break;
> > +
> > case X86_IRQ_ALLOC_TYPE_MSI:
> > case X86_IRQ_ALLOC_TYPE_MSIX:
> > - if (info->type == X86_IRQ_ALLOC_TYPE_HPET)
> > - set_hpet_sid(irte, info->hpet_id);
> > - else
> > - set_msi_sid(irte, info->msi_dev);
> > -
> > - msg->address_hi = MSI_ADDR_BASE_HI;
> > - msg->data = sub_handle;
> > - msg->address_lo = MSI_ADDR_BASE_LO |
> MSI_ADDR_IR_EXT_INT |
> > - MSI_ADDR_IR_SHV |
> > - MSI_ADDR_IR_INDEX1(index) |
> > - MSI_ADDR_IR_INDEX2(index);
> > + set_msi_sid(irte, info->msi_dev);
> > + irte_prepare_msg(msg, index, sub_handle);
> > + break;
> > +
> > + case X86_IRQ_ALLOC_TYPE_DEV_MSI:
> > + irte_prepare_msg(msg, index, sub_handle);
> > break;
> >
> > default:
> >
> > Hmm?
>
> It'd get a bit nicer if you *always* did the irte_prepare_msg() part to
> generate the MSI message. Let the IOAPIC driver swizzle that into the
> IOAPIC RTE for itself. You have no business composing an IOAPIC RTE
> here.
>
> Then your switch statement is *only* for setting the SID in the IRTE
> appropriately.

I don’t think I fully understand what needs to be done, but if we move the IOAPIC RTE configure into the IOAPIC driver, wouldn't that mean that the IOAPIC driver should be aware of interrupt remapping?

Right now IOAPIC case here configures an RTE entry, and the MSI related cases configure the msi message(through the irte_prepare_msg()). So unless irte_prepare_msg somehow even configures IOAPIC message, we cannot always do irte_prepare_msg right?

It would be great if you could provide some insight here ????

Thanks,
Megha