From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] Re: KVM call agenda for May 18 Date: Tue, 18 May 2010 16:50:15 -0500 Message-ID: <4BF30B97.7080608@codemonkey.ws> References: <20100518032346.GK4992@x200.localdomain> <4BF29BCF.4050805@codemonkey.ws> <20100518140927.GJ8328@redhat.com> <4BF2A55E.5030001@codemonkey.ws> <4BF2CEFD.20804@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Daniel P. Berrange" , Chris Wright , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail-vw0-f46.google.com ([209.85.212.46]:37686 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754234Ab0ERVuT (ORCPT ); Tue, 18 May 2010 17:50:19 -0400 Received: by vws9 with SMTP id 9so3226714vws.19 for ; Tue, 18 May 2010 14:50:18 -0700 (PDT) In-Reply-To: <4BF2CEFD.20804@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/18/2010 12:31 PM, Avi Kivity wrote: > On 05/18/2010 05:34 PM, Anthony Liguori wrote: >> >> No. I don't think our goal is to ever fully convert monitor commands >> to QMP. Some commands simply don't make sense as QMP commands (like >> x and xp). > > Examining memory does make sense for QMP, although it is already > available through the gdb protocol, so it's kind of redundant. The x and xp commands are meant to be used with all sorts of expressions. I agree examining memory makes sense but we certainly want a very different interface for it. Regards, Anthony Liguori