All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: Alistair <alistair@alistair23.me>, qemu-devel@nongnu.org
Cc: Zhao Liu <zhao1.liu@intel.com>
Subject: Re: QEMU Sashiko
Date: Thu, 29 Oct 2026 09:06:45 +0100	[thread overview]
Message-ID: <de5dd85c-e486-40b3-a0ce-613cc102089d@oss.qualcomm.com> (raw)
In-Reply-To: <bfacc761620e29347af03f3b613c6c877b4c1862.camel@alistair23.me>

On 29/10/26 00:32, Alistair wrote:
> Hey,
> 
> Sashiko just merged initial support for QEMU [1].
> 
> For those who don't know, Sashiko is a LLM powered review bot used for
> the Linux kernel. When people send patches to LKML Sashiko reviews the
> patches and responds to the mailing list with any issue that it finds.
> 
> Like all LLM tools, it is both useful, but also verbose, prone to
> hallucinations and misses things (like humans do to though). The
> general consensus in the kernel community is that it's a useful and
> valuable tool.
> 
> Sashiko is just a Rust application and prompts, it doesn't include a
> LLM and you can use a range of different LLM backends.
> 
> Google sponsors the development and runs a Linux instance. So you can
> see the hosted Linux instance here: https://sashiko.dev/ and it uses
> Gemini for the LLM which Google pays for. It seems like there is also a
> GCC one starting up.
> 
> The cool thing about Sashiko though is you can run it locally as well,
> so you can use it to test your patches before sending them to LKML, as
> long as you have a LLM backend you can use.
> 
> So, now that Sashiko also supports QEMU there are two exciting use
> cases:
> 
> 1. Developers can run it locally to review their patches before sending
> them to the list. This can catch issues before sending patches
> 
> 2. Maintainers can run an instance to review patches. How you set this
> up depends on the maintainer and how many tokens you have. Pointing it
> at the list directly and running it for all patches might be too much,
> but some combination of manually triggering it for certain patches
> seems to work well. The Settings.toml file can be setup based on what
> you want to do.
> 
> The hope with this is to save maintainers time as Sashiko can catch
> issues without requiring much time from a maintainer.
> 
> QEMU support in Sashiko is very new, so it will take some tweaking to
> improve things, but it is at least a good starting place.
> 
> 1:
> https://github.com/sashiko-dev/sashiko/commit/e432036bba7ab10d4517385916e6c834d8176f70

I'm glad you added projects/qemu/ directory there; some time ago
Zhao and myself tried to leverage LLM to review QEMU and reduce
maintenance burden but there was little community interest and
some negative feedback so we didn't pursued on the list.
https://lore.kernel.org/qemu-devel/afxbDjQEWJZ6P9oe@redhat.com/
https://lore.kernel.org/qemu-devel/arpINtziWCbjENeo@intel.com/



  reply	other threads:[~2026-10-29  8:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 23:32 QEMU Sashiko Alistair
2026-10-29  8:06 ` Philippe Mathieu-Daudé [this message]
2026-10-29 13:29   ` Fabiano Rosas
2026-10-29 12:50 ` Alex Bennée
2026-10-29 23:24   ` Alistair
2026-10-29 12:58 ` Daniel P. Berrangé
2026-10-29 23:28   ` Alistair
2026-10-29 13:35 ` Brian Cain
2026-10-29 14:01   ` Marc-André Lureau

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=de5dd85c-e486-40b3-a0ce-613cc102089d@oss.qualcomm.com \
    --to=philmd@oss.qualcomm.com \
    --cc=alistair@alistair23.me \
    --cc=qemu-devel@nongnu.org \
    --cc=zhao1.liu@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.