public inbox for virtualization@lists.linux-foundation.org 
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen•com>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: "David Hildenbrand (Arm)" <david@kernel•org>,
	 Pasha Tatashin <pasha.tatashin@soleen•com>,
	Lance Yang <lance.yang@linux•dev>,
	peterz@infradead•org,  dave.hansen@intel•com,
	dave.hansen@linux•intel.com, ypodemsk@redhat•com,
	 hughd@google•com, will@kernel•org, aneesh.kumar@kernel•org,
	npiggin@gmail•com,  tglx@linutronix•de, mingo@redhat•com,
	bp@alien8•de, x86@kernel•org, hpa@zytor•com,  arnd@arndb•de,
	ljs@kernel•org, ziy@nvidia•com, baolin.wang@linux•alibaba.com,
	 Liam.Howlett@oracle•com, npache@redhat•com,
	ryan.roberts@arm•com, dev.jain@arm•com,  baohua@kernel•org,
	shy828301@gmail•com, riel@surriel•com, jannh@google•com,
	 jgross@suse•com, seanjc@google•com, pbonzini@redhat•com,
	 boris.ostrovsky@oracle•com, virtualization@lists•linux.dev,
	kvm@vger•kernel.org,  linux-arch@vger•kernel.org,
	linux-mm@kvack•org, linux-kernel@vger•kernel.org,
	 ioworker0@gmail•com, roman.gushchin@linux•dev
Subject: Re: [PATCH 7.2 v10 0/2] skip redundant sync IPIs when TLB flush sent them
Date: Fri, 24 Apr 2026 10:40:49 -0400	[thread overview]
Message-ID: <aeuAwkNsmDer08MD@google.com> (raw)
In-Reply-To: <20260424073145.b990fe9b925da304508aad71@linux-foundation.org>

On 04-24 07:31, Andrew Morton wrote:
> On Fri, 24 Apr 2026 16:20:55 +0200 "David Hildenbrand (Arm)" <david@kernel•org> wrote:
> 
> > On 4/24/26 16:15, Andrew Morton wrote:
> > > On Fri, 24 Apr 2026 13:37:04 +0000 Pasha Tatashin <pasha.tatashin@soleen•com> wrote:
> > > 
> > >> On 04-24 06:30, Andrew Morton wrote:
> > >>>
> > >>>
> > >>> Sashiko questions:
> > >>> 	https://sashiko.dev/#/patchset/20260424062528.71951-1-lance.yang@linux.dev
> > >>>
> > >>> (I never know if my Sashiko emails are welcome/useful.  Maybe Sashiko
> > >>> said the same stuff about v9 and it's all wrong.  But better safe than
> > >>> sorry!)
> > >>
> > >> These emails are helpful; but, I do not believe you should have to 
> > >> manually follow up with a link to every new patch series.
> > >>
> > >> Perhaps  Sashiko could automatically send a summary email in response to 
> > >> the cover letter, or provide a link once the reviews are complete. For 
> > >> the kexec ML, we opted-in with Roman to receive automated emails from 
> > >> sashiko.
> > > 
> > > Yep.  I'd be OK with an automatic reply-to-all.  Maybe some won't like
> > > that.
> > > 
> > > An alternative I've discussed with Roman is an automated
> > > reply-to-author with a cc to a dedicated list (we could use mm-commits
> > > for now).
> > > 
> > > Preferences?
> > 
> > Reply-to-author would likely be better as a first step.
> 
> Why do you think so?
> 
> Pasha, is it too early to determine how reply-to-all is working out for
> kexec?

It is too early, we have opted-in only at the end of last week.

Pasha

  reply	other threads:[~2026-04-24 14:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  6:25 [PATCH 7.2 v10 0/2] skip redundant sync IPIs when TLB flush sent them Lance Yang
2026-04-24  6:25 ` [PATCH 7.2 v10 1/2] mm/mmu_gather: prepare to skip redundant sync IPIs Lance Yang
2026-04-24 15:04   ` Peter Zijlstra
2026-04-24 15:52     ` Dave Hansen
2026-05-27  1:44       ` Andrew Morton
2026-04-24 15:40   ` Lance Yang
2026-04-24  6:25 ` [PATCH 7.2 v10 2/2] x86/tlb: skip redundant sync IPIs for native TLB flush Lance Yang
2026-04-24 15:12   ` Peter Zijlstra
2026-04-24 15:49     ` Lance Yang
2026-04-24 13:30 ` [PATCH 7.2 v10 0/2] skip redundant sync IPIs when TLB flush sent them Andrew Morton
2026-04-24 13:37   ` Pasha Tatashin
2026-04-24 14:15     ` Andrew Morton
2026-04-24 14:20       ` David Hildenbrand (Arm)
2026-04-24 14:31         ` Andrew Morton
2026-04-24 14:40           ` Pasha Tatashin [this message]
2026-04-24 18:36           ` David Hildenbrand (Arm)
2026-04-24 18:50             ` Yosry Ahmed
2026-04-24 19:01               ` Peter Zijlstra
2026-04-24 19:12                 ` Zi Yan
2026-04-24 19:15                   ` Yosry Ahmed
2026-04-25  0:58                     ` SeongJae Park
2026-04-24 19:22                   ` Peter Zijlstra
2026-04-24 19:35                     ` Peter Zijlstra
2026-04-24 20:03                       ` Roman Gushchin
2026-04-24 20:11                         ` Peter Zijlstra
2026-05-29 11:10                           ` Peter Zijlstra
2026-04-24 19:08               ` Andrew Morton
2026-04-24 19:09               ` David Hildenbrand (Arm)
2026-04-24 19:17                 ` Peter Zijlstra
2026-04-24 19:24                   ` David Hildenbrand (Arm)
2026-04-24 19:18                 ` Yosry Ahmed
2026-04-25  1:12                   ` SeongJae Park
2026-04-25  5:17                   ` David Hildenbrand (Arm)
2026-04-25 11:36                     ` Andrew Morton
2026-04-27  8:53                       ` David Hildenbrand (Arm)
2026-04-25  1:19           ` SeongJae Park

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=aeuAwkNsmDer08MD@google.com \
    --to=pasha.tatashin@soleen$(echo .)com \
    --cc=Liam.Howlett@oracle$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=aneesh.kumar@kernel$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=baohua@kernel$(echo .)org \
    --cc=baolin.wang@linux$(echo .)alibaba.com \
    --cc=boris.ostrovsky@oracle$(echo .)com \
    --cc=bp@alien8$(echo .)de \
    --cc=dave.hansen@intel$(echo .)com \
    --cc=dave.hansen@linux$(echo .)intel.com \
    --cc=david@kernel$(echo .)org \
    --cc=dev.jain@arm$(echo .)com \
    --cc=hpa@zytor$(echo .)com \
    --cc=hughd@google$(echo .)com \
    --cc=ioworker0@gmail$(echo .)com \
    --cc=jannh@google$(echo .)com \
    --cc=jgross@suse$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=lance.yang@linux$(echo .)dev \
    --cc=linux-arch@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=ljs@kernel$(echo .)org \
    --cc=mingo@redhat$(echo .)com \
    --cc=npache@redhat$(echo .)com \
    --cc=npiggin@gmail$(echo .)com \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=peterz@infradead$(echo .)org \
    --cc=riel@surriel$(echo .)com \
    --cc=roman.gushchin@linux$(echo .)dev \
    --cc=ryan.roberts@arm$(echo .)com \
    --cc=seanjc@google$(echo .)com \
    --cc=shy828301@gmail$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    --cc=virtualization@lists$(echo .)linux.dev \
    --cc=will@kernel$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    --cc=ypodemsk@redhat$(echo .)com \
    --cc=ziy@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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