From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for May 18
Date: Tue, 18 May 2010 20:31:41 +0300
Message-ID: <4BF2CEFD.20804@redhat.com>
References: <20100518032346.GK4992@x200.localdomain> <4BF29BCF.4050805@codemonkey.ws> <20100518140927.GJ8328@redhat.com> <4BF2A55E.5030001@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Chris Wright <chrisw@redhat.com>, qemu-devel@nongnu.org,
	kvm@vger.kernel.org
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:10789 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754516Ab0ERRbu (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 18 May 2010 13:31:50 -0400
In-Reply-To: <4BF2A55E.5030001@codemonkey.ws>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.