From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v2] kvm: remove redundant registration of BSP's hv_clock area Date: Tue, 18 Feb 2014 12:06:35 +0100 Message-ID: <53033EBB.4000205@redhat.com> References: <1392363424.24711.2.camel@nexus> <530323EC.2030800@redhat.com> <1392718151.12070.2.camel@nexus> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Marcelo Tosatti , kvm@vger.kernel.org To: =?UTF-8?B?RmVybmFuZG8gTHVpcyBWw6F6cXVleiBDYW8=?= Return-path: Received: from mail-qc0-f181.google.com ([209.85.216.181]:51324 "EHLO mail-qc0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754466AbaBRLOT (ORCPT ); Tue, 18 Feb 2014 06:14:19 -0500 Received: by mail-qc0-f181.google.com with SMTP id e9so25517814qcy.12 for ; Tue, 18 Feb 2014 03:14:19 -0800 (PST) In-Reply-To: <1392718151.12070.2.camel@nexus> Sender: kvm-owner@vger.kernel.org List-ID: Il 18/02/2014 11:09, Fernando Luis V=C3=A1zquez Cao ha scritto: > These days hv_clock allocation is memblock based (i.e. the percpu > allocator is not involved), which means that the physical address > of each of the per-cpu hv_clock areas is guaranteed to remain > unchanged through all its lifetime and we do not need to update > its location after CPU bring-up. > > Signed-off-by: Fernando Luis Vazquez Cao > --- > > diff -urNp linux-3.14-rc3-orig/arch/x86/kernel/kvm.c linux-3.14-rc3/a= rch/x86/kernel/kvm.c > --- linux-3.14-rc3-orig/arch/x86/kernel/kvm.c 2014-02-18 19:01:08.103= 189324 +0900 > +++ linux-3.14-rc3/arch/x86/kernel/kvm.c 2014-02-18 19:01:45.41249436= 6 +0900 > @@ -417,7 +417,6 @@ void kvm_disable_steal_time(void) > #ifdef CONFIG_SMP > static void __init kvm_smp_prepare_boot_cpu(void) > { > - WARN_ON(kvm_register_clock("primary cpu clock")); > kvm_guest_cpu_init(); > native_smp_prepare_boot_cpu(); > kvm_spinlock_init(); > diff -urNp linux-3.14-rc3-orig/arch/x86/kernel/kvmclock.c linux-3.14-= rc3/arch/x86/kernel/kvmclock.c > --- linux-3.14-rc3-orig/arch/x86/kernel/kvmclock.c 2014-01-20 11:40:0= 7.000000000 +0900 > +++ linux-3.14-rc3/arch/x86/kernel/kvmclock.c 2014-02-18 19:02:51.966= 823212 +0900 > @@ -242,7 +242,7 @@ void __init kvmclock_init(void) > hv_clock =3D __va(mem); > memset(hv_clock, 0, size); > > - if (kvm_register_clock("boot clock")) { > + if (kvm_register_clock("primary cpu clock")) { > hv_clock =3D NULL; > memblock_free(mem, size); > return; > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Thanks, applying to kvm/queue. Paolo