All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Kevin Loughlin <kevinloughlin@google.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com,  bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com,  pbonzini@redhat.com,
	kirill.shutemov@linux.intel.com, kai.huang@intel.com,
	 ubizjak@gmail.com, jgross@suse.com, kvm@vger.kernel.org,
	 thomas.lendacky@amd.com, pgonda@google.com,
	sidtelang@google.com,  mizhang@google.com, rientjes@google.com,
	manalinandan@google.com,  szy0127@sjtu.edu.cn
Subject: Re: [PATCH v5 0/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency
Date: Tue, 25 Feb 2025 17:35:54 -0800	[thread overview]
Message-ID: <Z75v-hT5SxKlqdwt@google.com> (raw)
In-Reply-To: <20250123002422.1632517-1-kevinloughlin@google.com>

On Thu, Jan 23, 2025, Kevin Loughlin wrote:
> v5:
> - explicitly encode wbnoinvd as 0xf3 0x0f 0x09 for binutils backwards compatibility

Please, please, please do not send new series with In-Reply-To.  Trying to sort
through the different versions in my workflow was painful.  From
Documentation/process/maintainer-kvm-x86.rst:

Links
~~~~~
Do not explicitly reference bug reports, prior versions of a patch/series, etc.
via ``In-Reply-To:`` headers.  Using ``In-Reply-To:`` becomes an unholy mess
for large series and/or when the version count gets high, and ``In-Reply-To:``
is useless for anyone that doesn't have the original message, e.g. if someone
wasn't Cc'd on the bug report or if the list of recipients changes between
versions.

To link to a bug report, previous version, or anything of interest, use lore
links.  For referencing previous version(s), generally speaking do not include
a Link: in the changelog as there is no need to record the history in git, i.e.
put the link in the cover letter or in the section git ignores.  Do provide a
formal Link: for bug reports and/or discussions that led to the patch.  The
context of why a change was made is highly valuable for future readers.

      parent reply	other threads:[~2025-02-26  1:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 22:55 [PATCH v2 0/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-01-09 22:55 ` [PATCH v2 1/2] x86, lib: Add WBNOINVD helper functions Kevin Loughlin
2025-01-09 22:55 ` [PATCH v2 2/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-01-10  8:23   ` Kirill A. Shutemov
2025-01-13 18:47     ` Kevin Loughlin
2025-01-14  7:50       ` Kirill A. Shutemov
2025-01-14 16:12         ` Sean Christopherson
2025-01-17 22:20           ` Kevin Loughlin
2025-01-13 21:46   ` Mingwei Zhang
2025-01-22  0:13 ` [PATCH v3 0/2] " Kevin Loughlin
2025-01-22  0:13   ` [PATCH v3 1/2] x86, lib: Add WBNOINVD helper functions Kevin Loughlin
2025-01-22  0:30     ` Dave Hansen
2025-01-22  0:30       ` Dave Hansen
2025-01-22  1:14       ` Kevin Loughlin
2025-01-22  0:13   ` [PATCH v3 2/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-01-22  1:34   ` [PATCH v4 0/2] " Kevin Loughlin
2025-01-22  1:34     ` [PATCH v4 1/2] x86, lib: Add WBNOINVD helper functions Kevin Loughlin
2025-01-22  7:32       ` Kirill A. Shutemov
2025-01-22 19:39         ` Tom Lendacky
2025-01-22 23:16           ` Dave Hansen
2025-01-23  0:06             ` Kevin Loughlin
2025-01-23  0:33               ` Dave Hansen
2025-01-23  0:58                 ` Kevin Loughlin
2025-01-23  1:17                   ` Kevin Loughlin
2025-01-22  1:34     ` [PATCH v4 2/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-01-23  0:24     ` [PATCH v5 0/2] " Kevin Loughlin
2025-01-23  0:24       ` [PATCH v5 1/2] x86, lib: Add WBNOINVD helper functions Kevin Loughlin
2025-01-23  0:36         ` Dave Hansen
2025-01-23  0:55           ` Kevin Loughlin
2025-01-23  0:24       ` [PATCH v5 2/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-02-26  1:30         ` Sean Christopherson
2025-02-01  0:02       ` [PATCH v6 0/2] " Kevin Loughlin
2025-02-01  0:02         ` [PATCH v6 1/2] x86, lib: Add WBNOINVD helper functions Kevin Loughlin
2025-02-04 16:59           ` Tom Lendacky
2025-02-26  1:26           ` Sean Christopherson
2025-02-26 14:22             ` Borislav Petkov
2025-02-01  0:02         ` [PATCH v6 2/2] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Kevin Loughlin
2025-02-04 17:00           ` Tom Lendacky
2025-02-26  1:35       ` Sean Christopherson [this message]

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=Z75v-hT5SxKlqdwt@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=kai.huang@intel.com \
    --cc=kevinloughlin@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manalinandan@google.com \
    --cc=mingo@redhat.com \
    --cc=mizhang@google.com \
    --cc=pbonzini@redhat.com \
    --cc=pgonda@google.com \
    --cc=rientjes@google.com \
    --cc=sidtelang@google.com \
    --cc=szy0127@sjtu.edu.cn \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=ubizjak@gmail.com \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.