it seems msi_domain_alloc_irqs is successful and get the MSI-X interrupt,
but when to activate this interrupt, it reports the call trace warning.
And I checked the tx/rx with command: ethtool -S enp0s0f0 (the interface
name), I can find there are package received and send out some packages,
but there is not any interrupt generated.
# ethtool -S enp0s0f0
NIC statistics:
SI rx octets: 94258
SI rx frames: 510
SI rx u-cast frames: 47
SI rx m-cast frames: 17
SI tx octets: 41367
SI tx frames: 179
SI tx u-cast frames: 0
SI tx m-cast frames: 45
On Monday, October 18, 2021 at 4:36:20 PM UTC+8 Changming Huang wrote:
> thanks kiszka.
> I checked the boot log, and find one call trace during MSI-X activate:
> [ 2.333986] Call trace:
> [ 2.333988] valid_col+0x14/0x24
> [ 2.333992] its_send_single_command+0x4c/0x150
> [ 2.333997] its_irq_domain_activate+0xb8/0xf0
> [ 2.334002] __irq_domain_activate_irq+0x5c/0xac
> [ 2.334007] __irq_domain_activate_irq+0x38/0xac
> [ 2.334011] irq_domain_activate_irq+0x3c/0x64
> [ 2.334014] __msi_domain_alloc_irqs+0x198/0x350
> [ 2.334019] msi_domain_alloc_irqs+0x1c/0x30
> [ 2.334023] __pci_enable_msix_range+0x614/0x6a0
> [ 2.334027] pci_alloc_irq_vectors_affinity+0xbc/0x13c
> [ 2.334030] enetc_alloc_msix+0x40/0x270
> [ 2.334037] enetc_pf_probe+0x6d0/0xf00
>
> there is not any issue in root-cell boot log.
>
> which can cause this issue?
> On Monday, October 18, 2021 at 1:50:59 PM UTC+8 [email protected]
> wrote:
>
>> On 18.10.21 04:13, Changming Huang wrote:
>> > MSI-X vectors translates the interrupt through its, the GIC and my
>> > network device DTS node in root cell:
>> > gic: interrupt-controller@6000000 {
>> > compatible= "arm,gic-v3";
>> > #address-cells = <2>;
>> > #size-cells = <2>;
>> > ranges;
>> > reg= <0x0 0x06000000 0 0x10000>, /* GIC Dist */
>> > <0x0 0x06040000 0 0x40000>; /* GIC
>> Redistributor */
>> > #interrupt-cells= <3>;
>> > interrupt-controller;
>> > interrupts = <GIC_PPI 9 (GIC_CPU_MASK_RAW(0xf) |
>> > IRQ_TYPE_LEVEL_LOW)>;
>> > its: gic-its@6020000 {
>> > compatible = "arm,gic-v3-its";
>> > msi-controller;
>> > reg = <0x0 0x06020000 0 0x20000>;/* GIC
>> > Translater */
>> > };
>> > };
>> >
>> > enetc_pcie: pcie@1f0000000 { /* Integrated Endpoint
>> > Root Complex */
>> > compatible = "pci-host-ecam-generic";
>> > reg = <0x01 0xf0000000 0x0 0x100000>;
>> > #address-cells = <3>;
>> > #size-cells = <2>;
>> > msi-parent = <&its>;
>> > device_type = "pci";
>> > bus-range = <0x0 0x0>;
>> > dma-coherent;
>> > msi-map = <0 &its 0x17 0xe>;
>> > ...
>> > }
>> >
>> > and I copy them all related nodes into cell DTS.
>> >
>> > so, I need more effort on MSI-X in cell?
>>
>> This is conceptually the right thing, but something must be missing.
>>
>> Is the ITS recognized by the non-root Linux kernel? Is that kernel
>> identical to the root-cell one (just to exclude configuration issues)?
>> Compare the boot logs.
>>
>> Jan
>>
>> --
>> Siemens AG, T RDA IOT
>> Corporate Competence Center Embedded Linux
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/f8ae1dec-47ba-43f3-babf-9de6e66709cen%40googlegroups.com.
