From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBmkt-0001Tg-UF for qemu-devel@nongnu.org; Fri, 07 Feb 2014 09:50:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBmkl-0003sc-Hp for qemu-devel@nongnu.org; Fri, 07 Feb 2014 09:50:11 -0500 Received: from mail-qa0-x236.google.com ([2607:f8b0:400d:c00::236]:47254) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBmkl-0003nS-D8 for qemu-devel@nongnu.org; Fri, 07 Feb 2014 09:50:03 -0500 Received: by mail-qa0-f54.google.com with SMTP id i13so5382553qae.27 for ; Fri, 07 Feb 2014 06:50:02 -0800 (PST) Sender: Richard Henderson Message-ID: <52F4F27F.5000703@twiddle.net> Date: Fri, 07 Feb 2014 06:49:35 -0800 From: Richard Henderson MIME-Version: 1.0 References: <20140131160902.32741.2680.stgit@fimbulvetr.bsc.es> <52F0FFBD.8050801@twiddle.net> <87k3davcs3.fsf@fimbulvetr.bsc.es> <52F3B105.80908@twiddle.net> <87a9e411r9.fsf@fimbulvetr.bsc.es> In-Reply-To: <87a9e411r9.fsf@fimbulvetr.bsc.es> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 00/12] trace: [tcg] Allow tracing guest events in TCG-generated code List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, Stefan Hajnoczi On 02/06/2014 11:26 AM, Lluís Vilanova wrote: >> > At which point, option 2 would be the best bet, I think. > Right. For the 3rd option I was also thinking about having per-vCPU tracing > states (in the case of guest events), so that you can trace separate events > depending on the vCPU. > > Which reminds me, I should add a vCPU pointer to the "guest_vmem" event, since > otherwise you cannot differentiate accesses among different vCPUs. The TB cache is shared, so you won't be able to do option 3 for different events for different cpus. You could only do option 1 for that. r~