From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHHOj-0002Lu-07 for qemu-devel@nongnu.org; Thu, 07 Jan 2016 15:43:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aHHOf-0002KL-Jv for qemu-devel@nongnu.org; Thu, 07 Jan 2016 15:43:04 -0500 Received: from mx2.parallels.com ([199.115.105.18]:52904) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHHOf-0002He-ES for qemu-devel@nongnu.org; Thu, 07 Jan 2016 15:43:01 -0500 References: <1452174932-28657-1-git-send-email-den@openvz.org> <568E9AB8.6000701@redhat.com> From: "Denis V. Lunev" Message-ID: <568ECDC8.9030304@openvz.org> Date: Thu, 7 Jan 2016 23:42:48 +0300 MIME-Version: 1.0 In-Reply-To: <568E9AB8.6000701@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 00/11] simplify usage of tracepoints, and connect them to logging List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com On 01/07/2016 08:04 PM, Eric Blake wrote: > On 01/07/2016 06:55 AM, Denis V. Lunev wrote: >> This series does three things: >> >> 1) add a "-trace [enable=]foo" option to enable one or more trace >> events, and a "-trace help" option to show the list of tracepoints >> (patches 4-5) >> >> 2) change the stderr tracing backend so that it prints to the >> -D log file, and enable it by default. "-trace file=..." is >> now a synonym of -D if the log backend is enabled (patches 7-8) >> >> 3) add a "-d trace:foo" option that is a synonym for "-trace foo"; >> this makes the new functionality more discoverable to people used >> to "-d", makes it available for user-mode emulation (which does >> not have -trace), and is somewhat nice if you want to enable both >> tracepoints and some other "-d" flag (patch 9). When globbing >> it is also less susceptible to unwanted shell expansion. >> >> For example, you can trace block device I/O and save the result >> to a file just by adding "-trace bdrv_aio_*,file=trace.txt", or >> correlate it to guest PCs with "-d exec,nochain,trace:bdrv_aio_*". >> >> Opinions? I would like to have this in 2.5 if there is agreement. > Stale sentence :) > copy/paste forever :)