Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp56956pxu; Tue, 1 Dec 2020 06:07:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJxyBvvSZmhgAmVHs2GerhSxTFI5DBuYmmO1Fd7uU68DurpScfvdO0UNwUT5jmGDZWzOECWr X-Received: by 2002:a19:cc16:: with SMTP id c22mr1261675lfg.75.1606831662737; Tue, 01 Dec 2020 06:07:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606831662; cv=none; d=google.com; s=arc-20160816; b=I3pwZRT12vPPf5oB3gc418zBhksd3P23Q1ytDQUsZ717J+/2KuhV07l7gj3PP6oO/j 6SdPF6IT2OIXYo6koDuV17dqPM5tlqU3aOrieecyaXRSaCo/kKZa523VFpzJoa5lHPDq gBDhjl8QDYIgCeI2sfOfNiQNYFmkknXkOg7R55FBr+DHJm18FEHcg1y9YUGzyZBCJsr1 D+ePPK6aDk12rHg89y0lm+FUspdDj57eSQbG1vHKFcqbKQOwjtN2Y6Pl+AJcWv5iXqss VSd7UzRPCEZf4VAtMn4QMXBVA3RIT/vaDbJii3W8iGXo9QkRjmsymn8zSFJ18JVkrf9/ Eg5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=fH6vXaLD6JyknYN6wcvlAFebplSlI6lIoEByMQneE7k=; b=UCUVmLfFjzUjtQZEkoOZDsuL7EV62GH78BCGWwF+Ilyc5sd9nOkMYXwIORUwqPv57s 3Dorbo/joLCFmawaRBZNgNXg5s7/uH0qw5hVTSBpz6/SDFfZrRllXX7G5cm+FAahXfDn +ocbE58KNlI6pb3cQsJJJR8YpsxrWi43C+nYdXlMsxgb/ktgy95cG6ThbavyWJP4uWTj C1GSlvK6N1zy/dYFI38Loj42oeEtFPFSSYrsJZvmTk2HMnaoergOAvV9374uopNJ94wR VG9eVHU/dkS6oMO41eVB29R9qHL7+YL3B05YWtcCfrMq/YABGotKH/rbET+krCusrw/q yivw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=fU4+RFcp; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=B3+oM+PS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h4si1146442edv.124.2020.12.01.06.07.19; Tue, 01 Dec 2020 06:07:42 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=fU4+RFcp; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=B3+oM+PS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391323AbgLAOCJ (ORCPT + 99 others); Tue, 1 Dec 2020 09:02:09 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:55688 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387628AbgLAOCI (ORCPT ); Tue, 1 Dec 2020 09:02:08 -0500 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1606831286; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fH6vXaLD6JyknYN6wcvlAFebplSlI6lIoEByMQneE7k=; b=fU4+RFcpBzVQQkeBKxd/Z/TsfI8RUL4LYY0e4bzgz3Pa1bkvofiWij5DmBKKl6FOMhDabI kfVpDrLL3Jpgea5HXO+V16KwjaHZMHXJokQkhT6hHhkqSS8ceRCHEUBuYB4uqYL6yHO8/a lmlI5DQmf/OcBfaw4Ivys0TzWPCs1Oif00okWbaXjln88J7mU5aa5OLQB0OTFiYH6d7b2M neJHfQEwDf3DB5ZJgNIJgqNnU+tneurZwM2mDSLzDmUYfwIctWX9qI69H6NgmsoRPbYvbG c4XKYpcf+lexocSv18EjARBjBL/m6Wek3pVTVqXNXJjOwJikyKLWsq1P3tI48Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1606831286; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fH6vXaLD6JyknYN6wcvlAFebplSlI6lIoEByMQneE7k=; b=B3+oM+PSmOc0/ILm8QfBvak9HqhEGOT2w6vw/hq52ePbm/hmMA6AF8BmdcrH9ECvWuV36H tnnUOfz5fw0lyKCQ== To: Marcelo Tosatti , Maxim Levitsky Cc: kvm@vger.kernel.org, Paolo Bonzini , Oliver Upton , Ingo Molnar , Sean Christopherson , open list , Jonathan Corbet , Wanpeng Li , Borislav Petkov , Jim Mattson , "H. Peter Anvin" , "open list\:DOCUMENTATION" , Joerg Roedel , "maintainer\:X86 ARCHITECTURE \(32-BIT AND 64-BIT\)" , Vitaly Kuznetsov Subject: Re: [PATCH 0/2] RFC: Precise TSC migration In-Reply-To: <20201130191643.GA18861@fuller.cnet> References: <20201130133559.233242-1-mlevitsk@redhat.com> <20201130191643.GA18861@fuller.cnet> Date: Tue, 01 Dec 2020 15:01:26 +0100 Message-ID: <874kl5hbgp.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 30 2020 at 16:16, Marcelo Tosatti wrote: > Not really. The synchronization logic tries to sync TSCs during > BIOS boot (and CPU hotplug), because the TSC values are loaded > sequentially, say: > > CPU realtime TSC val > vcpu0 0 usec 0 > vcpu1 100 usec 0 > vcpu2 200 usec 0 That's nonsense, really. > And we'd like to see all vcpus to read the same value at all times. Providing guests with a synchronized and stable TSC on a host with a synchronized and stable TSC is trivial. Write the _same_ TSC offset to _all_ vcpu control structs and be done with it. It's not rocket science. The guest TSC read is: hostTSC + vcpu_offset So if the host TSC is synchronized then the guest TSCs are synchronized as well. If the host TSC is not synchronized, then don't even try. Thanks, tglx