From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53986) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXnuC-0003IB-Lo for qemu-devel@nongnu.org; Wed, 19 Jul 2017 08:16:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dXnu9-00070o-Dg for qemu-devel@nongnu.org; Wed, 19 Jul 2017 08:16:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38306) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dXnu9-00070f-6p for qemu-devel@nongnu.org; Wed, 19 Jul 2017 08:16:37 -0400 Date: Wed, 19 Jul 2017 13:16:28 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20170719121628.GI2103@work-vm> References: <201707191247531805742@zte.com.cn> <20170719061651.GE2757@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170719061651.GE2757@localhost.localdomain> Subject: Re: [Qemu-devel] [PATCH v2] hmp: allow cpu index for "info lapic" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: wang.yi59@zte.com.cn, qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net, Liu.Jianjun3@zte.com.cn, liu.yunh@zte.com.cn * Eduardo Habkost (ehabkost@redhat.com) wrote: > On Wed, Jul 19, 2017 at 12:47:53PM +0800, wang.yi59@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 > > >> Signed-off-by: Yun Liu > > > > > > > >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 / dgilbert@redhat.com / Manchester, UK