From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 2/6] kvm: x86: drop read_tsc_offset() Date: Tue, 20 Sep 2016 07:37:43 +0200 Message-ID: References: <1474036056-21270-1-git-send-email-lcapitulino@redhat.com> <1474036056-21270-3-git-send-email-lcapitulino@redhat.com> <41e7b724-07dd-9c9d-3119-c12e50adbe44@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Luiz Capitulino , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , rostedt@goodmis.org, mhiramat@kernel.org, mtosatti@redhat.com To: Jim Mattson Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 20/09/2016 00:18, Jim Mattson wrote: > Hmmm. Yes, I think it does. With this patch series, > vcpu->arch.tsc_offset appears to contain L1's TSC offset (perhaps > making vmx->nested.vmcs01_tsc_offset redundant). > > However, this unfortunately limits the newly added functionality to > merging host and *L1* guest traces. It doesn't work with L2 (or > deeper) guests. Or perhaps I'm missing something? You can merge L1/L2 first and then host/L1. Paolo