* Eduardo Habkost (ehabk...@redhat.com) wrote: > On Wed, Jul 19, 2017 at 12:47:53PM +0800, 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. > > The "cpu" command is supposed to allow you to select the CPU for > those commands. Doesn't it work?
In the other arm to the thread Yi explained that they were driving it via virsh qemu-monitor-command, and I've just tried and it doesn't seem to work; doing: virsh qemu-monitor-command --domain rhel6.8 --hmp --cmd "cpu 1" virsh qemu-monitor-command --domain rhel6.8 --hmp --cmd "info lapic" dumping local APIC state for CPU 0 Dave > -- > Eduardo -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
