Hi On Thu, Oct 29, 2026 at 3:32 AM Alistair <[email protected]> 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.
Have you made a request for QEMU? Apparently, Roman is taking care of the various deployments, reaching out to him. Would it be possible to add it? QEMU patches are roughly ~25 series/day (usually a few patches, sometime up to 100). At first, we probably want a silent instance (not sending review mails) for evaluation and compliance checks. thanks > 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 > > Alistair > -- Marc-André Lureau
