mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Like Xu <like.xu.linux@gmail.com>
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
Subject: Re: [PATCH v2] KVM: x86/intr: Explicitly check NMI from guest to eliminate false positives
Date: Thu, 7 Dec 2023 10:12:46 +0800	[thread overview]
Message-ID: <6cd419ff-97d9-495b-bc9c-0c53c4b1e3d1@gmail.com> (raw)
In-Reply-To: <ZXCTppx4II1sbRAl@google.com>

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.

  reply	other threads:[~2023-12-07  2:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  3:20 Like Xu
2023-12-06 15:30 ` Sean Christopherson
2023-12-07  2:12   ` Like Xu [this message]
2023-12-07 16:31     ` Sean Christopherson
2023-12-07 15:32 ` Maxim Levitsky
2023-12-13  7:28 ` Dongli Zhang
2023-12-13  8:24   ` Like Xu
2023-12-13 17:01     ` Sean Christopherson
2024-02-06 19:38 ` Sean Christopherson
2024-02-06 21:08   ` Sean Christopherson
2024-02-18  9:51     ` Like Xu
2024-02-27  0:11       ` Sean Christopherson
2024-02-27  2:21 ` Sean Christopherson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6cd419ff-97d9-495b-bc9c-0c53c4b1e3d1@gmail.com \
    --to=like.xu.linux@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®