From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755798AbdLOJbC (ORCPT ); Fri, 15 Dec 2017 04:31:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55684 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755632AbdLOJa7 (ORCPT ); Fri, 15 Dec 2017 04:30:59 -0500 From: Vitaly Kuznetsov To: Paolo Bonzini , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" Cc: kvm@vger.kernel.org, x86@kernel.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , "Michael Kelley \(EOSG\)" , Andy Lutomirski , Mohammed Gamal , Cathy Avery , Roman Kagan , linux-kernel@vger.kernel.org, devel@linuxdriverproject.org Subject: Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V References: <20171213150945.24054-1-vkuznets@redhat.com> Date: Fri, 15 Dec 2017 10:30:54 +0100 In-Reply-To: (Paolo Bonzini's message of "Fri, 15 Dec 2017 10:01:06 +0100") Message-ID: <87r2rw2v8x.fsf@vitty.brq.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 15 Dec 2017 09:30:59 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paolo Bonzini writes: > On 13/12/2017 16:09, Vitaly Kuznetsov wrote: >> Currently, KVM passes PVCLOCK_TSC_STABLE_BIT to its guests when running in >> so called 'masterclock' mode and this is only possible when the clocksource >> on the host is TSC. When running nested on Hyper-V we're using a different >> clocksource in L1 (Hyper-V TSC Page) which can actually be used for >> masterclock. This series brings the required support. >> >> Making KVM work with TSC page clocksource is relatively easy, it is done in >> PATCH 5 of the series. All the rest is required to support L1 migration > ^^^^^^^ > > Patch 6. :) > Off-by-one :-) >> when TSC frequency changes, we use a special feature from Hyper-V to do >> the job. > > Patches 5-7 are > > Acked-by: Paolo Bonzini > Thanks! > I would appreciate if the Hyper-V folks can provide a topic branch to be > merged in both HV and KVM trees. > There's no such thing as Hyper-V tree, patches are usually getting merged through 'tip' tree when the majority of changes go to arch/x86 or Greg's char-misc tree when changes are drivers/hv heavy (+ net, scsi, pci, hid, ... trees for individual drivers). In this particular case the series is x86-heavy and I believe it should go through x86 'tip' tree. Thomas, Ingo, Peter, could you please take a look? Thanks! -- Vitaly