Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: "Pranjal Shrivastava" <praan@google.com>,
	"Tianrui Zhao" <zhaotianrui@loongson.cn>,
	"Bibo Mao" <maobibo@loongson.cn>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Madhavan Srinivasan" <maddy@linux.ibm.com>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Atish Patra" <atish.patra@linux.dev>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Janosch Frank" <frankja@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"David Hildenbrand" <david@kernel.org>,
	"Vitaly Kuznetsov" <vkuznets@redhat.com>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Paul Durrant" <paul@xen.org>,
	"Eric Farman" <farman@linux.ibm.com>,
	"Matthew Rosato" <mjrosato@linux.ibm.com>,
	"Halil Pasic" <pasic@linux.ibm.com>,
	"Nipun Gupta" <nipun.gupta@amd.com>,
	"Nikhil Agarwal" <nikhil.agarwal@amd.com>,
	"Alex Williamson" <alex@shazbot.org>,
	"Ioana Ciornei" <ioana.ciornei@nxp.com>,
	"Longfang Liu" <liulongfang@huawei.com>,
	"Julian Ruess" <julianr@linux.ibm.com>,
	"Kirti Wankhede" <kwankhede@nvidia.com>,
	"Yishai Hadas" <yishaih@nvidia.com>,
	"Ankit Agrawal" <ankita@nvidia.com>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	"Shameer Kolothum" <skolothumtho@nvidia.com>,
	"Kevin Tian" <kevin.tian@intel.com>,
	"Brett Creeley" <brett.creeley@amd.com>,
	"Eric Auger" <eric.auger@redhat.com>,
	"Mostafa Saleh" <smostafa@google.com>,
	"Giovanni Cabiddu" <giovanni.cabiddu@intel.com>,
	"David Matlack" <dmatlack@google.com>,
	"Michał Winiarski" <michal.winiarski@intel.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"Kiryl Shutsemau" <kas@kernel.org>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Rick Edgecombe" <rick.p.edgecombe@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Roman Gushchin" <kfree@google.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sashiko review email for kvm@vger.kernel.org?
Date: Wed, 20 May 2026 19:54:31 +0100	[thread overview]
Message-ID: <20260520195431.6ec8e6df@pumpkin> (raw)
In-Reply-To: <ag3GY3P0SgZPF_IJ@google.com>

On Wed, 20 May 2026 14:34:11 +0000
Sean Christopherson <seanjc@google.com> wrote:

> +KVM and LKML (to capture as many of these discussions possible)
> 
> On Wed, May 20, 2026, Pranjal Shrivastava wrote:
> > On Tue, May 19, 2026 at 12:18:17AM +0000, Sean Christopherson wrote:  
> > > Hello people with a MAINTAINERS entry that uses kvm@vger.kernel.org as a mailing list!
> > > 
> > > How would y'all feel about enabling Sashiko[*] emails for kvm@vger.kernel.org?  For
> > > a variety of reasons, Sashiko currently only logs its reviews to https://sashiko.dev
> > > by default.  If subsystems want to receive on-list mails, they need to opt-in.
> > > 
> > > I really, really want to enable email reviews for KVM x86, as Sashiko has found
> > > an almost embarassing number of bugs that (a) would have been painful to debug
> > > had they escaped review and (b) I'm not convinced would have been found by
> > > traditional review.  And for me at least the signal:noise ratio is more than good
> > > enough.  There are still hallucinations and false positives from time to time,
> > > but the good outweighs the bad by quite a bit, it's cathartic to flame AI when
> > > it's wrong, and worst case scenario I can simply ignore Sashiko.
> > > 
> > > But, currently Sashiko is only capable of making decisions based on mailing list,
> > > i.e. as things stand, _all_ of kvm@ needs to opt-in.  Before I badger Roman to
> > > add bespoke logic to Sashiko's email flow, e.g. to special case KVM x86 in some
> > > way, I want to see if there's a general consensus in favor (or against) enabling
> > > review emails.  
> > 
> > I vote for enabling it, it has proven helpful at multiple places. I
> > would wanna ratelimit the # emails it may send in case of a malfunction
> > though.  
> 
> Ya, there's definitely an implied "we'll turn it back off if there are major
> problems".  But I don't see any reason to treat Sashiko any differently than
> other automated systems in this regard; when bots have been too noisy in the
> past, we've complained, and the bot/system was "fixed".
> 

Given the number of emails to lkml a few more won't hurt :-)
But perhaps they should come from "Sashiko (AI bot)" to remind everyone on
every email.

-- David

      parent reply	other threads:[~2026-05-20 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <agusSarZr-R_o2xD@google.com>
     [not found] ` <fbb937ae-62e4-4386-86fb-67d9b85c8fdc@linux.ibm.com>
2026-05-19 20:25   ` Sashiko review email for kvm@vger.kernel.org? Sean Christopherson
2026-05-21  9:32     ` Janosch Frank
2026-05-21 10:55       ` Paolo Bonzini
     [not found] ` <ag0H28jSbSTHXznK@google.com>
2026-05-20 14:34   ` Sean Christopherson
2026-05-20 14:43     ` Pranjal Shrivastava
2026-05-20 18:54     ` David Laight [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=20260520195431.6ec8e6df@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=alex@shazbot.org \
    --cc=ankita@nvidia.com \
    --cc=anup@brainfault.org \
    --cc=atish.patra@linux.dev \
    --cc=borntraeger@linux.ibm.com \
    --cc=brett.creeley@amd.com \
    --cc=chenhuacai@kernel.org \
    --cc=cohuck@redhat.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@kernel.org \
    --cc=dmatlack@google.com \
    --cc=dwmw2@infradead.org \
    --cc=eperezma@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=giovanni.cabiddu@intel.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=jasowang@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=julianr@linux.ibm.com \
    --cc=kas@kernel.org \
    --cc=kevin.tian@intel.com \
    --cc=kfree@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liulongfang@huawei.com \
    --cc=maddy@linux.ibm.com \
    --cc=maobibo@loongson.cn \
    --cc=michal.winiarski@intel.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=mst@redhat.com \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=npiggin@gmail.com \
    --cc=pasic@linux.ibm.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=praan@google.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=sgarzare@redhat.com \
    --cc=skolothumtho@nvidia.com \
    --cc=smostafa@google.com \
    --cc=stefanha@redhat.com \
    --cc=vkuznets@redhat.com \
    --cc=yishaih@nvidia.com \
    --cc=zhaotianrui@loongson.cn \
    /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