From: Kiryl Shutsemau <kas@kernel.org>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: pbonzini@redhat.com, dave.hansen@intel.com, seanjc@google.com,
x86@kernel.org, adrian.hunter@intel.com, yan.y.zhao@intel.com,
binbin.wu@intel.com, xiaoyao.li@intel.com, chao.gao@intel.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
nik.borisov@suse.com, yilun.xu@linux.intel.com,
tony.lindgren@linux.intel.com
Subject: Re: [PATCH v2 0/2] Drop unneeded cache flushing
Date: Wed, 21 Oct 2026 11:09:23 +0100 [thread overview]
Message-ID: <atiPBtAVRC9hHXFm@thinkstation> (raw)
In-Reply-To: <20261015191710.3632302-1-rick.p.edgecombe@intel.com>
On Thu, Oct 15, 2026 at 12:17:08PM -0700, Rick Edgecombe wrote:
> Yilun's comment about cleaning up the TDR reclaim after the changes in
> patch 2 was a bit bigger that I expected. I really debated whether to
> split that out. But it wasn't very feasible to do it as a prep patch, so I
> left it as one big bigger. Really debated doing that, or an follow up
> cleanup patch. Opinions requested.
I am fine with one patch.
For the series:
Reviewed-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-10-21 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 19:17 [PATCH v2 0/2] Drop unneeded cache flushing Rick Edgecombe
2026-10-15 19:17 ` [PATCH v2 1/2] x86/virt/tdx: Drop tdx_clflush_*() Rick Edgecombe
2026-10-20 10:56 ` Xu Yilun
2026-10-15 19:17 ` [PATCH v2 2/2] x86/virt/tdx: Drop tdh_phymem_page_wbinvd_*() Rick Edgecombe
2026-10-20 8:55 ` Binbin Wu
2026-10-20 10:55 ` Xu Yilun
2026-10-19 8:36 ` [PATCH v2 0/2] Drop unneeded cache flushing Nikolay Borisov
2026-10-21 10:09 ` Kiryl Shutsemau [this message]
2026-10-22 9:11 ` Tony Lindgren
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=atiPBtAVRC9hHXFm@thinkstation \
--to=kas@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=binbin.wu@intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tony.lindgren@linux.intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=yan.y.zhao@intel.com \
--cc=yilun.xu@linux.intel.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 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.