From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH 0/4] paravirt clock patches Date: Tue, 13 May 2008 08:53:43 +0200 Message-ID: <48293AF7.5010304@redhat.com> References: <1209026228-9113-1-git-send-email-kraxel@redhat.com> <20080428192816.GA4596@dmt> <4821F8B8.7050601@redhat.com> <20080508231045.GA6429@dmt> <482450BB.3050409@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti , andi-suse@firstfloor.org To: Glauber Costa Return-path: In-Reply-To: <482450BB.3050409@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Glauber Costa wrote: > So maybe declare the per-cpu areas in a special section, then in > setup_per_cpu_areas, copy them into the definitive per-cpu section and > update the callers? The special section and the copy is implemented already. That doesn't cut it for the kvmclock case though. We registered the physical address via msr write in the host, and *that* needs an update too. Otherwise the host continues to update the pre-setup location, and the guest sees the (stale) values the kvm clock had at per-cpu-area-setup time (when the copy took place). cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/