Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Message-ID: <6cd419ff-97d9-495b-bc9c-0c53c4b1e3d1@gmail.com>
Date:   Thu, 7 Dec 2023 10:12:46 +0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v2] KVM: x86/intr: Explicitly check NMI from guest to
 eliminate false positives
Content-Language: en-US
To:     Sean Christopherson <seanjc@google.com>
Cc:     Paolo Bonzini <pbonzini@redhat.com>,
        Andi Kleen <ak@linux.intel.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <20231206032054.55070-1-likexu@tencent.com>
 <ZXCTppx4II1sbRAl@google.com>
From:   Like Xu <like.xu.linux@gmail.com>
In-Reply-To: <ZXCTppx4II1sbRAl@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/12/2023 11:30 pm, Sean Christopherson wrote:
> Please don't make up random prefixes.  This should really be "x86/pmu".

Thanks.

I'm hesitant to categorize about NMI handling into kvm/pmu scope. But you
have clear idea on it and it's fine to me. Please feel free to refine commit
message to fit your understanding and taste as you did.

> 
>  From Documentation/process/maintainer-kvm-x86.rst:
> 
> Shortlog
> ~~~~~~~~
> The preferred prefix format is ``KVM: <topic>:``, where ``<topic>`` is one of::
> 
>    - x86
>    - x86/mmu
>    - x86/pmu
>    - x86/xen
>    - selftests
>    - SVM
>    - nSVM
>    - VMX
>    - nVMX
> 
> 
> ...
> 
> New topics do occasionally pop up, but please start an on-list discussion if
> you want to propose introducing a new topic, i.e. don't go rogue.