Re: PCI/kernel msi code vs GIC ITS driver conflict?

From: John Garry
Date: Thu Sep 05 2019 - 10:53:49 EST



>
> root@(none)$ echo 0000:74:02.0 > ./sys/bus/pci/drivers/hisi_sas_v3_hw/unbind
>
> <snip>
>
> [ 34.806156] Freed devid 7410 LPI 0
> [ 34.809555] Freed devid 7410 LPI 0
> [ 34.812951] Freed devid 7410 LPI 0
> [ 34.816344] Freed devid 7410 LPI 0
> [ 34.819734] Freed devid 7410 LPI 0
> [ 34.823122] Freed devid 7410 LPI 0
> [ 34.826512] Freed devid 7410 LPI 0
> [ 34.829901] Freed devid 7410 LPI 0
> [ 34.833291] Freed devid 7410 LPI 0
> [ 34.836680] Freed devid 7410 LPI 0
> [ 34.840071] Freed devid 7410 LPI 0
> [ 34.843461] Freed devid 7410 LPI 0
> [ 34.846848] Freed devid 7410 LPI 0
> [ 34.850238] Freed devid 7410 LPI 0
> [ 34.853627] Freed devid 7410 LPI 0
> [ 34.857017] Freed devid 7410 LPI 0
> [ 34.860406] Freed devid 7410 LPI 0
> [ 34.863797] Unmap devid 7410 shared 0 lpi_map
> [ 34.868229] Unmap devid 7410
> root@(none)$
> root@(none)$
> root@(none)$ echo 0000:74:02.0 > ./sys/bus/pci/drivers/hisi_sas_v3_hw/bind
> [ 39.158802] scsi host0: hisi_sas_v3_hw
> [ 40.383384] ITS: alloc 9920:32
> [ 40.386429] ITT 32 entries, 5 bits
> [ 40.389970] ID:0 pID:9920 vID:23
> [ 40.393188] ID:1 pID:9921 vID:24
> [ 40.396404] ID:2 pID:9922 vID:25
> [ 40.399621] ID:3 pID:9923 vID:26
> [ 40.402836] ID:4 pID:9924 vID:27
> [ 40.406053] ID:5 pID:9925 vID:28
> [ 40.409269] ID:6 pID:9926 vID:29
> [ 40.412485] ID:7 pID:9927 vID:30
> [ 40.415702] ID:8 pID:9928 vID:31
> [ 40.418916] ID:9 pID:9929 vID:32
> [ 40.422132] ID:10 pID:9930 vID:33
> [ 40.425435] ID:11 pID:9931 vID:34
> [ 40.428739] ID:12 pID:9932 vID:35
> [ 40.432042] ID:13 pID:9933 vID:36
> [ 40.435345] ID:14 pID:9934 vID:37
> [ 40.438648] ID:15 pID:9935 vID:38
> [ 40.441951] ID:16 pID:9936 vID:39
>
>
> <snip>
Awesome. Can I take this as a Tested-by?

Sure, btw, could you please also add:

Reported-by: Jiaxing Luo <luojiaxing@xxxxxxxxxx>

... as he did initial discovery and analysis on the problem.



> Btw, I hacked the "Freed devid %x event %d LPI %ld\n" print to remove
> the "event" value, as you may have noticed.
Yup, not meaningful for the problem at hand.

Thanks again for your help!


Thanks for the help,
John

M.