From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60588) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMhZw-00054T-1x for qemu-devel@nongnu.org; Tue, 04 Aug 2015 15:08:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMhZn-0005yv-IN for qemu-devel@nongnu.org; Tue, 04 Aug 2015 15:08:48 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:37680) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMhZn-0005yj-Ca for qemu-devel@nongnu.org; Tue, 04 Aug 2015 15:08:39 -0400 Received: by wibud3 with SMTP id ud3so36419859wib.0 for ; Tue, 04 Aug 2015 12:08:38 -0700 (PDT) References: <1438593291-27109-1-git-send-email-alex.bennee@linaro.org> <1438593291-27109-4-git-send-email-alex.bennee@linaro.org> <20150804121616.GA8192@aurel32.net> <87h9ofks0j.fsf@linaro.org> <55C0D879.90404@twiddle.net> <87d1z3klyh.fsf@linaro.org> <55C0FFE2.5010502@twiddle.net> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: <55C0FFE2.5010502@twiddle.net> Date: Tue, 04 Aug 2015 20:08:36 +0100 Message-ID: <87a8u6lvm3.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v4 03/11] qemu-log: correct help text for -d cpu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: Peter Maydell , QEMU Trivial , QEMU Developers , Peter Crosthwaite , Paolo Bonzini , Aurelien Jarno Richard Henderson writes: > On 08/04/2015 10:22 AM, Alex Bennée wrote: >> >> Richard Henderson writes: >> >>> On 08/04/2015 08:15 AM, Peter Maydell wrote: >>>> On 4 August 2015 at 16:11, Alex Bennée wrote: >>>>> Aurelien Jarno writes: >>>>>> On 2015-08-03 10:14, Alex Bennée wrote: >>>>>> In practice this is not true for linked TB. Should we also disable TB >>>>>> linking when this option is enabled? >>>>> >>>>> Good question. I suspect yes because if you've gone to level of wanting >>>>> exec tracing you'll probably get confused by the chaining. Of course it >>>>> will run a lot slower then. >>>> >>>> Unless the bug you were trying to track down is caused by the exec >>>> chaining, of course... But yes, I think we get more people wanting >>>> chaining to be disableable. >>>> >>>> Not sure we want to tie it to the 'cpu' debug option, though -- it >>>> applies just as much to 'exec'. >>> >>> Does it make more sense to have a 'nochain' debug option, and not tie it to >>> either 'cpu' or 'exec'? It might be occasionally useful on its own, simply to >>> determine if a bug does exist in the exec chaining. >> >> Would that make sense as a debug option or should we have a specific set >> of TCG options to alter its behaviour? > > > That's what I'm saying -- probably a separate debug option is better. Sorry I meant should we add it to -d (as in -d nochain) or have some tcg opts (--tcg nochain,blah) > > > r~ -- Alex Bennée