From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55277) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1IFQ-0005gX-2z for qemu-devel@nongnu.org; Wed, 07 Sep 2011 09:33:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R1IFP-0005Nh-2L for qemu-devel@nongnu.org; Wed, 07 Sep 2011 09:33:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65378) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R1IFO-0005NK-Qs for qemu-devel@nongnu.org; Wed, 07 Sep 2011 09:32:59 -0400 Date: Wed, 7 Sep 2011 16:33:51 +0300 From: "Michael S. Tsirkin" Message-ID: <20110907133351.GE10510@redhat.com> References: <4E66402C.2020900@siemens.com> <4E66417E.6040308@codemonkey.ws> <20110906160903.GA21675@redhat.com> <4E664A19.5000207@codemonkey.ws> <20110906170529.GA22871@redhat.com> <4E673B50.5080908@redhat.com> <20110907130625.GA10510@redhat.com> <4E676DDC.3030006@siemens.com> <20110907131737.GC10510@redhat.com> <4E67703E.8070902@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E67703E.8070902@codemonkey.ws> Subject: Re: [Qemu-devel] [PATCH 0/6] Device state visualization reloaded List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , Anthony Liguori , qemu-devel , Jan Kiszka , Markus Armbruster , Luiz Capitulino On Wed, Sep 07, 2011 at 08:23:10AM -0500, Anthony Liguori wrote: > On 09/07/2011 08:17 AM, Michael S. Tsirkin wrote: > >On Wed, Sep 07, 2011 at 03:13:00PM +0200, Jan Kiszka wrote: > >>On 2011-09-07 15:06, Michael S. Tsirkin wrote: > >>>But if the command is not for users at all, if it's > >>>for qemu debugging, then exposing internals is a very > >>>logical thing. Only problem is - we must make it very very clear > >>>which commands are for qemu debugging. > >> > >>This command it also for users, to debug guests. > >> > >>Jan > > > >Hmm, guest visible state must be stable by definition. > >So why can't we make the interfaces stable then? > > Because right now how you reference devices cannot be stable. For devices that do have IDs, we can support this on QMP as well then? -- MST