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 03D54C3DA7D for ; Tue, 3 Jan 2023 16:31:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237602AbjACQbN (ORCPT ); Tue, 3 Jan 2023 11:31:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54242 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233316AbjACQbI (ORCPT ); Tue, 3 Jan 2023 11:31:08 -0500 Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A27BFEC for ; Tue, 3 Jan 2023 08:31:02 -0800 (PST) Received: by mail-pj1-x102b.google.com with SMTP id j8-20020a17090a3e0800b00225fdd5007fso21988270pjc.2 for ; Tue, 03 Jan 2023 08:31:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=HuXJyRgtnlne85q3+aPwkSR/XYTZCRo5Z2w1+rQP9ao=; b=COSMKscwkWtMhthuZAUrWwSumX4QHSdink89cmgYtdZ54m0ePB1EGKwl0STLVEQWW6 NgZNRIxcjfnvcXeDn5ccFCpgjrgUl5TFg0e++IiG39fXXne/c+SVcyHwAIKhU7OlO9By MJmG0DGPkOsz3Kb/qvsVAXIfJckymJOugHCTttGDrPkRyN7/3RA02aqnZSMTF3VvqGJy 7jQaX92dO8yS65MFqfQjMY6ySf1i7zrUS+L0cTtTsDAb1EenLR8xw8+WPzFwp+qIrvQM GgpbYRmfjO5SOw4jMO7qhaNdm7Shd21GkTq7NhgMie/k/++P6BKVRpVMDeAD1qWR9Z7o h6jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=HuXJyRgtnlne85q3+aPwkSR/XYTZCRo5Z2w1+rQP9ao=; b=aUzGzuREXkOLPJLVjL0+bGMGF3JxUtQlERJJdGTa3tEnM5h9ug7ySJHbWJfhvCKTJs PyFyjVo36kUkkuPeIzrXRDgp4/PgW6/KIXw0MQSNvcNg1YgCJ3u75ZX7OOeHHM5awu4R 0ua7ZURvHHh+16/LCjPHV8jYsQobbrx1LYg5hD+hPddh7RrEnjF3NtCd+nNc0Ya/jU/O 1dSsNhvQQxQ7kqzzUBqYEsVyuu2Iz5q/fZheaiw9cQiNjmNTBaviMBHTTS+CfEaIgXJq iF+Pu4uJVeEPOlbVrcuCfHvOoeufUXtWarOtjNlPEKGNJxL+SF1VpDqe5onjXapaPaX7 YxtA== X-Gm-Message-State: AFqh2koFaGmDoT4iqQBbXVuut0bAviQUSv2dWegdExyqwA9lDFVGZzZ7 Ml7tRUx+yunG+YAwK9cww2bXSw== X-Google-Smtp-Source: AMrXdXuWZN8/EEkW2DrzxGb9ocfW7DG+NJAEwqhQ3RLSkXwbYYD1VKcvpbO8nNWgHWjX/j7lfk6lUQ== X-Received: by 2002:a05:6a21:3942:b0:9d:b8e6:d8e5 with SMTP id ac2-20020a056a21394200b0009db8e6d8e5mr3865007pzc.2.1672763461683; Tue, 03 Jan 2023 08:31:01 -0800 (PST) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id cp12-20020a170902e78c00b00187022627d7sm22451092plb.36.2023.01.03.08.31.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Jan 2023 08:31:01 -0800 (PST) Date: Tue, 3 Jan 2023 16:30:57 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: Maxim Levitsky , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Alejandro Jimenez , Suravee Suthikulpanit , Li RongQing Subject: Re: [PATCH v4 11/32] KVM: x86: Inhibit APIC memslot if x2APIC and AVIC are enabled Message-ID: References: <20221001005915.2041642-1-seanjc@google.com> <20221001005915.2041642-12-seanjc@google.com> <90d4a2a1733cdb21e7c00843ddafee78ce52bbdc.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Dec 27, 2022, Paolo Bonzini wrote: > On 12/16/22 20:40, Sean Christopherson wrote: > > I was hoping to have a name that communicate_why_ the memslot needs to be > > inhibited, but it's turning out to be really hard to come up with a name that's > > descriptive without being ridiculously verbose. The best I've come up with is: > > > > allow_apicv_in_x2apic_without_x2apic_virtualization > > > > It's heinous, but I'm inclined to go with it unless someone has a better idea. > > Can any of you provide a patch to squash on top of this one (or on top of > kvm/queue, as you prefer)? I'll send patches, though it might take a day or three. I had a reworked version of this series prepped and tested before vacation kicked in, but lost power before I could send my traditional pre-vacation patch bomb :-/