* wang.y...@zte.com.cn (wang.y...@zte.com.cn) wrote:
> Hi Eduardo,
>
> Thank you for your reply!
>
> >On Mon, Jul 17, 2017 at 09:49:37PM -0400, Yi Wang wrote:
>
> >> Add [vcpu] index support for hmp command "info lapic", which is
>
> >> useful when debugging ipi and so on. Current behavior is not
>
> >> changed when the parameter isn't specified.
>
> >>
>
> >> Signed-off-by: Yi Wang <wang.y...@zte.com.cn>
>
> >> Signed-off-by: Yun Liu <liu.y...@zte.com.cn>
>
> >
>
> >We have 8 monitor commands (see below) that use the CPU set by
> >the "cpu" command (mon_get_cpu()) as input. Why is "info lapic"
> >special?
>
> When we debugging a problem of ipi, we wanted to verify lapic info
> on each vCPU, but we found that we could only get vCPU 0's lapic
> through "info lapic", so we supposed this patch could help those
> who have the same problem as us.
I think Eduardo's point is that you can already do:
cpu 0
info lapic
cpu 1
info lapic
Dave
>
>
>
>
> >
>
> >* info cpustats
>
> >* info lapic
>
> >* info mem
>
> >* info registers
>
> >* info tlb
>
> >* x
>
> >* memsave
>
> >* inject-nmi (QMP)
>
> Monitor command "info registers" already have "-a" parameter to
>
> show all vCPU's info. -)
>
> May I send some new patches for the other monitor commands, which may
>
> be helpful for analyzing multiple cpu problems?
>
>
>
>
>
> ---
>
> Best wishes
>
> Yi Wang
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
