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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 77C6DC54EAA for ; Thu, 26 Jan 2023 20:47:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229784AbjAZUrG (ORCPT ); Thu, 26 Jan 2023 15:47:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52914 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229731AbjAZUrF (ORCPT ); Thu, 26 Jan 2023 15:47:05 -0500 Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E0CA573768 for ; Thu, 26 Jan 2023 12:46:29 -0800 (PST) Received: by mail-oi1-x22a.google.com with SMTP id r205so2492908oib.9 for ; Thu, 26 Jan 2023 12:46:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=65oEAScgUYAE8KruWPSkfRMTnDB8eV6fK8VEQc/uLFA=; b=OqPzMccJcZnZGD9WSHYzTRHjKzY/peIuHLKTZxjF1SbpcroX3gmzt1cOZAaiQP3hgg rEuzMwJ/xit6Z5huIjjhSuVMiajhrnubGWfIVXjx4T+t1jke2LskACy5zWmEBSSWo8tg OgSKk5lEsAkCjtQO7/kxN428i4RPZ50qavFbsKL4JS9yry7KYQZmTeqZaH3sfQp460bU FyczWfAVEx012VR5UUajmVfsfT1iW7fmPDFo/1N1n0deBP2zk+bron3Ws9MPuvht0vSi 8rdlRN76OWBrwc2N/sUPOWaadU7g5vDdEF867B1zDD246YOr3TD57eO86++Z1koYN4J5 DrcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=65oEAScgUYAE8KruWPSkfRMTnDB8eV6fK8VEQc/uLFA=; b=Za4NZ6J06khtAsPtUU5otXhl8xxf89tEmXUwluGrXxP4KT7XT2kqTonWN6k7g3E5ZQ +cq4pwFbTo1jFWEFwfWLo8P5V+csCjCleihxsR0cNXra3xjj87IdS3iJ8MpIQdZFnaKR pdfV4ljZCLxuha/JRjfGaASAyvBvkclohfCtkcWKqvV9Xg2vOJ9x/3/VdbZxTReAdgsW 7xje+uBjJggkn5d3KL6HQyFakn3K4dpOyvtVlyYbLsvWU4qlXqHPSEyzrfOCON367K6R kIpWMN7fIHk00tL/2PbqHVbQlwoo/rf6NwGCf7O8RgGiswZNub1zZtmwz2WkRDKcPrw+ 2UuA== X-Gm-Message-State: AFqh2krHOgeDMbkP6l7fEsGmBIMed9u2fxEoYp3w4845ajIUGC4HpeZ7 agDgmJpkustYqNYRXUf2ZRCn/IgBEYQNwAFgQZQ5AA== X-Google-Smtp-Source: AMrXdXs/BatnkOGFZ9IZFzSNd4aanhUQg5HHDKCp9DO+wxxsB56W1plvWBP556Lm07LkTjYUGD+fX439sciWUe3T6KA= X-Received: by 2002:aca:efc6:0:b0:36e:b85f:6081 with SMTP id n189-20020acaefc6000000b0036eb85f6081mr1299293oih.103.1674765970022; Thu, 26 Jan 2023 12:46:10 -0800 (PST) MIME-Version: 1.0 References: <20221027092036.2698180-1-pbonzini@redhat.com> <3a23db58-3ae1-7457-ed09-bc2e3f6e8dc9@redhat.com> <8bdf22c8-9ef1-e526-df36-9073a150669d@redhat.com> In-Reply-To: From: Jim Mattson Date: Thu, 26 Jan 2023 12:45:58 -0800 Message-ID: Subject: Re: [PATCH v2] KVM: x86: Do not return host topology information from KVM_GET_SUPPORTED_CPUID To: Paolo Bonzini Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, seanjc@google.com, stable@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Thu, Jan 26, 2023 at 9:47 AM Paolo Bonzini wrote: > > On 1/26/23 17:06, Jim Mattson wrote: > >>> Sadly, there isn't a single kernel involved. People running our VMM on > >>> their desktops are going to be impacted as soon as this patch hits > >>> that distro. (I don't know if I can say which distro that is.) So, now > >>> we have to get the VMM folks to urgently accommodate this change and > >>> get a new distribution out. > >> > >> Ok, this is what is needed to make a more informed choice. To be clear, > >> this is _still_ not public (for example it's not ChromeOS), so there is > >> at least some control on what version of the VMM they use? Would it > >> make sense to buy you a few months by deferring this patch to Linux 6.3-6.5? > > > > Mainline isn't a problem. I'm more worried about 5.19 LTS. > > 5.19 is not LTS, is it? This patch is only in 6.1.7 and 6.1.8 as far as > stable kernels is concerned, should I ask Greg to revert it there? It came to my attention when commit 196c6f0c3e21 ("KVM: x86: Do not return host topology information from KVM_GET_SUPPORTED_CPUID") broke some of our tests under 5.10 LTS. If it isn't bound for linux-5.19-y, then we have some breathing room.