From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58842)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1bZGVK-00030L-BC
	for qemu-devel@nongnu.org; Mon, 15 Aug 2016 07:56:31 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1bZGVG-0002fs-4M
	for qemu-devel@nongnu.org; Mon, 15 Aug 2016 07:56:29 -0400
Received: from gate.crashing.org ([63.228.1.57]:37103)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1bZGVF-0002fm-Qq
	for qemu-devel@nongnu.org; Mon, 15 Aug 2016 07:56:26 -0400
Message-ID: <1471262176.12231.102.camel@kernel.crashing.org>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Mon, 15 Aug 2016 21:56:16 +1000
In-Reply-To: <CAFEAcA9j2ghkdpq09doXLRTh90rAe9inzoTTBFa-pxxcuQoUQA@mail.gmail.com>
References: <1471089120.12231.48.camel@kernel.crashing.org>
	<CAFEAcA_oQLWwiqfGKbR8Bxf0Une+GrBNo0yNJS67oyccDJaWWQ@mail.gmail.com>
	<1471215342.12231.73.camel@kernel.crashing.org>
	<CAFEAcA-1zEMmHRErU==yyteic00nL=2yZ2NL66y-8dfaLfroJg@mail.gmail.com>
	<1471260884.12231.100.camel@kernel.crashing.org>
	<CAFEAcA9j2ghkdpq09doXLRTh90rAe9inzoTTBFa-pxxcuQoUQA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] monitor: Add an "xlate" command for
 translating a virtual address
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>

On Mon, 2016-08-15 at 12:44 +0100, Peter Maydell wrote:
> Certainly I think the QMP protocol command should just
> return all the info (I think current best-practice is
> to implement new HMP commands as wrappers round an
> equivalent QMP command). At that point we get into UI
> design questions about whether we should just print
> everything for the HMP command output, or have it default
> to just-address with an option to print with the attributes.
> I don't have a strong opinion there.

Ok I have no experience with QMP, I'll have a look, but from a UI
perspective, it's easier to not bother too much and just print it
all, something like:

translated_addr [secure=x,user=y,req_id=id]

This is low level debugging stuff, the user can cope with the verbose
output.

Ben.