On Wed, 19 Jul 2017 16:48:23 +0800 (CST)
<wang.yi59@xxxxxxxxxx> wrote:
> >* wang.yi59@xxxxxxxxxx (wang.yi59@xxxxxxxxxx) 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.yi59@xxxxxxxxxx>
>
> >>
>
> >> >> Signed-off-by: Yun Liu <liu.yunh@xxxxxxxxxx>
>
> >>
>
> >> >
>
> >>
>
> >> >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
>
> Yes, I get it, thank you.
>
> The reason of the problem we met is that we use "virsh qemu-monitor-command",
>
> so the 'cpu' command didn't work.
you can try to use qmp interface directly which supports specifying cpu for monitor commands:
qemu supports:
-- Command: human-monitor-command
Execute a command on the human monitor and return the output.
Arguments:
'command-line: string'
the command to execute in the human monitor
'cpu-index: int' (optional)
The CPU to use for commands that require an implicit CPU
maybe "virsh qemu-monitor-command" can also do it, CCing libvirt list
>
>
>
>
>
>
>
>
> ---
>
> Best wishes
>
> Yi Wang
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
