From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: [PATCH 27/30] nVMX: Additional TSC-offset handling Date: Mon, 09 May 2011 10:27:59 -0700 Message-ID: <4DC8241F.9090801@redhat.com> References: <1304842511-nyh@il.ibm.com> <201105080829.p488T5hi018362@rice.haifa.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, gleb@redhat.com, avi@redhat.com To: "Nadav Har'El" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33763 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752710Ab1EIR2F (ORCPT ); Mon, 9 May 2011 13:28:05 -0400 In-Reply-To: <201105080829.p488T5hi018362@rice.haifa.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/08/2011 01:29 AM, Nadav Har'El wrote: > In the unlikely case that L1 does not capture MSR_IA32_TSC, L0 needs to > emulate this MSR write by L2 by modifying vmcs02.tsc_offset. We also need to > set vmcs12.tsc_offset, for this change to survive the next nested entry (see > prepare_vmcs02()). > Both changes look correct to me. Zach