[Pdbg] [PATCH v4 18/30] main: Avoid printing top level "proc" if no child is enabled
Alistair Popple
alistair at popple.id.au
Wed Oct 9 15:30:29 AEDT 2019
> pdbg -a probe on any of the palm machines would produce following output:
>
> # pdbg -a probe
> proc0:
> fsi0: Kernel based FSI master (*)
> pib0: POWER FSI2PIB (*)
> core9: POWER8 Core (*)
> thread0: POWER8 Thread (*)
> thread1: POWER8 Thread (*)
> thread2: POWER8 Thread (*)
> thread3: POWER8 Thread (*)
> thread4: POWER8 Thread (*)
> thread5: POWER8 Thread (*)
> thread6: POWER8 Thread (*)
> thread7: POWER8 Thread (*)
> core11: POWER8 Core (*)
> thread0: POWER8 Thread (*)
> thread1: POWER8 Thread (*)
> thread2: POWER8 Thread (*)
> thread3: POWER8 Thread (*)
> thread4: POWER8 Thread (*)
> thread5: POWER8 Thread (*)
> thread6: POWER8 Thread (*)
> thread7: POWER8 Thread (*)
> core12: POWER8 Core (*)
> thread0: POWER8 Thread (*)
> thread1: POWER8 Thread (*)
> thread2: POWER8 Thread (*)
> thread3: POWER8 Thread (*)
> thread4: POWER8 Thread (*)
> thread5: POWER8 Thread (*)
> thread6: POWER8 Thread (*)
> thread7: POWER8 Thread (*)
> core13: POWER8 Core (*)
> thread0: POWER8 Thread (*)
> thread1: POWER8 Thread (*)
> thread2: POWER8 Thread (*)
> thread3: POWER8 Thread (*)
> thread4: POWER8 Thread (*)
> thread5: POWER8 Thread (*)
> thread6: POWER8 Thread (*)
> thread7: POWER8 Thread (*)
> proc1:
>
>
> Since proc1 is virtual, it gets enabled and printed in the output. This
patch is to avoid priting proc1 in the probe output.
Ok, figured this may have been the answer. But I think the probe should just
leave virtual nodes without any children disabled in the first place (must've
missed this when looking at that patch). Unless there is some other reason we
can't do this?
- Alistair
> Amitay.
>
More information about the Pdbg
mailing list