From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34077) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WT5XK-0002oB-KJ for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:19:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WT5XG-0008La-8V for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:19:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19158) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WT5XG-0008LW-0M for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:19:38 -0400 From: Markus Armbruster References: <1395844634-11729-1-git-send-email-alex.bennee@linaro.org> <1395844634-11729-2-git-send-email-alex.bennee@linaro.org> <20140326184550.GA23230@dorilex> Date: Thu, 27 Mar 2014 09:19:32 +0100 In-Reply-To: <20140326184550.GA23230@dorilex> (Leandro Dorileo's message of "Wed, 26 Mar 2014 18:45:50 +0000") Message-ID: <87k3bgt5nv.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC PATCH 1/4] qemu-log: correct help text for -d cpu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Leandro Dorileo Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org Leandro Dorileo writes: > On Wed, Mar 26, 2014 at 02:37:11PM +0000, alex.bennee@linaro.org wrote: >> From: Alex Benn=C3=A9e >>=20 >> This doesn't just dump CPU state on translation but on every block >> entrance. >>=20 >> Signed-off-by: Alex Benn=C3=A9e >>=20 >> diff --git a/qemu-log.c b/qemu-log.c >> index 797f2af..35bbb56 100644 >> --- a/qemu-log.c >> +++ b/qemu-log.c >> @@ -105,7 +105,7 @@ const QEMULogItem qemu_log_items[] =3D { >> { CPU_LOG_EXEC, "exec", >> "show trace before each executed TB (lots of logs)" }, >> { CPU_LOG_TB_CPU, "cpu", >> - "show CPU state before block translation" }, >> + "show CPU registers before each executed TB (lots of logs)" }, > > what about s/lots of logs/hight volume log/ or maybe s/lots of > logs/hight volume/ ? Alex is sticking to the precedence in CPU_LOG_EXEC's help. Feel free to improve, just keep them consistent. [...]