From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09792C43460 for ; Wed, 14 Apr 2021 17:57:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D5C7D6113B for ; Wed, 14 Apr 2021 17:57:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351391AbhDNR54 (ORCPT ); Wed, 14 Apr 2021 13:57:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51740 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234303AbhDNR5z (ORCPT ); Wed, 14 Apr 2021 13:57:55 -0400 Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 79198C061574 for ; Wed, 14 Apr 2021 10:57:33 -0700 (PDT) Received: by mail-pf1-x436.google.com with SMTP id i190so14253471pfc.12 for ; Wed, 14 Apr 2021 10:57:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=bAj/sTVeT3EOEooCD0PWAEK0DFdv0I+bmfSZB33mtXg=; b=YKlFCQU3jURALAoms83ymQ5gvp6uDIeOmXii2ecYlnaY3CnAEQDKyFe11bMpij/ofF bvcE6c0NQt8C52+fZhUpCcVnJ56ADwd3GERCw21jztW8ge7H6iLIBzEFVgznlUdxw7pO GnB2RNc+cUijVVBbHPc7yLqNlFJ0AMoPT8e7fYGjW9FbSCPVJ1tcmkf670aGeGhzLbfn G7uKAmN10uawEXHZM3WXgk4wuHT9TNL3FcnnsWId9Lb1R0zD2t6EvnECYZh87Y/ILFFp hF4BFmzeV/oh2/ylAWDVPXzudMJtVFR4Jeu2zXoaWZZYomQ6zGjEFAKEctcmfEEhgTAR Li3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=bAj/sTVeT3EOEooCD0PWAEK0DFdv0I+bmfSZB33mtXg=; b=Y+d5Jg9K/z4py7zDKsb8LJJ+sn013gIKQBuYWhDtBpr4qSuEIFmGgWgSUagRZtwWiO i8hjoZefsrLDcuriR9ypnTSu7wwWyYNqjC23m0LAXhjA9ynVIJxl0QXQOYs/Wv255J3a r4+QTSSRlCZ4sveBL9pW7OGa7uEDqiR0GEmx+HjXMtpJxbUh1FB8MD8V1fjYMT/XnpFJ N1BLwSSrt8UgOfyoN5IroUS7R9fEmhODcygcv5W6oRWcFhDymo4Q/MfP9xIclrQjt5lW 3nq2ZMIv4RBdKA0o9KAqamQOFOUCUT6kODPg4PcZam7/4/Ns5Bz/h/Wikk3hH9Qsza6f 1nBA== X-Gm-Message-State: AOAM533e7CA24Xyk5sZCVkHLj4zpRcYpMGC4vR5fjXZCUQzXfO6bmFoA 7GuNiURGE202t2hkM0M2WKf/QQ== X-Google-Smtp-Source: ABdhPJw2RarwNWS5+8HnwKiSHGAsEixnrKltiKCAYoveloZrH9siPOcI5DSj1R2t10EAC+2caMUGjQ== X-Received: by 2002:a63:c60a:: with SMTP id w10mr37908204pgg.421.1618423052870; Wed, 14 Apr 2021 10:57:32 -0700 (PDT) Received: from google.com (240.111.247.35.bc.googleusercontent.com. [35.247.111.240]) by smtp.gmail.com with ESMTPSA id r26sm110056pfq.17.2021.04.14.10.57.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Apr 2021 10:57:32 -0700 (PDT) Date: Wed, 14 Apr 2021 17:57:28 +0000 From: Sean Christopherson To: Thomas Gleixner Cc: Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Christian Borntraeger , Michael Tokarev Subject: Re: [RFC PATCH 0/7] KVM: Fix tick-based vtime accounting on x86 Message-ID: References: <20210413182933.1046389-1-seanjc@google.com> <87wnt4vkij.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87wnt4vkij.ffs@nanos.tec.linutronix.de> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 14, 2021, Thomas Gleixner wrote: > On Tue, Apr 13 2021 at 11:29, Sean Christopherson wrote: > > This is an alternative to Wanpeng's series[*] to fix tick-based accounting > > on x86. The approach for fixing the bug is identical: defer accounting > > until after tick IRQs are handled. The difference is purely in how the > > context tracking and vtime code is refactored in order to give KVM the > > hooks it needs to fix the x86 bug. > > > > x86 compile tested only, hence the RFC. If folks like the direction and > > there are no unsolvable issues, I'll cross-compile, properly test on x86, > > and post an "official" series. > > I like the final outcome of this, but we really want a small set of > patches first which actually fix the bug and is easy to backport and > then the larger consolidation on top. > > Can you sort that out with Wanpeng please? Will do.