Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, "Theodore Tso" <tytso@mit.edu>,
	Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
	ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc
Date: Wed, 22 Jul 2026 11:53:01 +0200	[thread overview]
Message-ID: <87h5lrgxky.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260719112924.2f97086d@foz.lan>

On Sun, 19 Jul 2026 11:29:24 +0200,
Mauro Carvalho Chehab wrote:
> 
> On Sat, 18 Jul 2026 11:26:27 +0200
> Takashi Iwai <tiwai@suse.de> wrote:
> 
> > On Fri, 17 Jul 2026 02:58:12 +0200,
> > Mauro Carvalho Chehab wrote:
> > >   
> > > > So it's one say to say, we should figure out how to try to run Sashiko
> > > > on a local LLM, using open-weight models.  But it's going to be a lot
> > > > easier to propose such a thing than to actually do it.  
> > > 
> > > The main point is: do we really need 671B parameters? Those models
> > > speak a lot of different languages, have medical databases, and a lot
> > > of other random knowledge that are useless for kernel development.
> > > 
> > > I've been playing for a while with qwen 3.6 with 24KB context size,
> > > 36B parameters (3B activated), 4bits kv quantization and it does produce
> > > some decent results. The main limitation is the context size: it is
> > > probably not big enough to test big files (*)
> > > 
> > > (*) my GPU has 16GB and it is not dedicated to LLM - still, it does
> > >     present results on a reasonable time (a couple of minutes) and
> > >     with decent precision.  
> > 
> > I've been testing the kernel commit reviews with 16GB VRAM GPU, too.
> > It's an agent program based on Chris Mason's review prompts, and
> > targeted mainly for the verifications of our backport patches.  The
> > main models I tried were Qwen-3.6 35B, Gemma-4 26B and GPT-OSS 20B
> > (all 4-bit quantized).  And, my conclusion was that even such small
> > models can catch real bugs.
> > 
> > Yes, there are definitely many false-positives, and they don't always
> > follow the recent changes.  Also they cover much less changes than
> > Sashiko.  So, the results must be read with lots of grains of salt :)
> > 
> > The code review is different from the code generation, and the agent
> > divides the tasks so that the model can concentrate on each small
> > single task.  With that, small models can achieve in some level, too.
> > 
> > 
> > FWIW, the agent code is found at
> >   https://github.com/tiwai/kernel-review-agent.git
> > 
> > with HTML renderer and console viewer programs
> >   https://github.com/tiwai/review-table-gen.git
> >   https://github.com/tiwai/kreview-ui-rs.git
> 
> I just did a Sashiko review test using Ollama locally after applying 
> this PR:
> 
> 	https://github.com/sashiko-dev/sashiko/pull/338
> 
> The code was AI generated with qwen3.6 with Claude Opus reasoning
> (hf.co/rico03/Qwen3.6-27B-Claude-Opus-Reasoning-Distilled-GGUF:Q4_K_M).
> 
> I'll try to play with it a little bit to see how it works with
> real patch reviews.

Thanks!  Let me know if you can compare the review results from
different models qualitatively.  It'd be interesting.


Takashi

  reply	other threads:[~2026-07-22  9:53 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 15:09 [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc Jonathan Corbet
2026-07-16 15:28 ` Sasha Levin
2026-07-16 16:08   ` Mark Brown
2026-07-16 16:24     ` Sasha Levin
2026-07-16 20:38       ` Laurent Pinchart
2026-07-17 14:09         ` Sasha Levin
2026-07-21 23:15           ` Laurent Pinchart
2026-07-22  0:23             ` Guenter Roeck
2026-07-17 14:25       ` Mark Brown
2026-07-21 23:58       ` Jori Koolstra
2026-07-22  0:57         ` Linus Torvalds
2026-07-22 14:20           ` Trond Myklebust
2026-07-23 14:15             ` Mark Brown
2026-07-22 17:48           ` Konstantin Ryabitsev
2026-07-22 19:15             ` Linus Torvalds
2026-07-23  0:26             ` Kees Cook
2026-07-23 13:10               ` Steven Rostedt
2026-07-23 14:30           ` Jori Koolstra
2026-07-16 18:36   ` Jonathan Corbet
2026-07-16 19:53     ` Mauro Carvalho Chehab
2026-07-16 23:59       ` Theodore Tso
2026-07-17  0:58         ` Mauro Carvalho Chehab
2026-07-17  2:27           ` Theodore Tso
2026-07-17  7:19             ` Mauro Carvalho Chehab
2026-07-19  9:01             ` Mauro Carvalho Chehab
2026-07-21 18:21               ` Mauro Carvalho Chehab
2026-07-18  9:26           ` Takashi Iwai
2026-07-19  9:29             ` Mauro Carvalho Chehab
2026-07-22  9:53               ` Takashi Iwai [this message]
2026-07-17 13:55         ` Konstantin Ryabitsev
2026-07-17 14:24           ` Andrew Lunn
2026-07-17 14:32             ` Konstantin Ryabitsev
2026-07-17 14:50               ` Andrew Lunn
2026-07-17 20:21           ` Theodore Tso
2026-07-18 12:54             ` Mauro Carvalho Chehab
2026-07-16 20:05     ` Bart Van Assche
2026-07-16 20:52       ` James Bottomley
2026-07-16 20:23     ` Liam R. Howlett
2026-07-17  7:49       ` Laurent Pinchart
2026-07-17 15:55         ` Liam R. Howlett
2026-07-17 11:57       ` James Bottomley
2026-07-17 15:53         ` Liam R. Howlett
2026-07-17 18:12           ` James Bottomley
2026-07-17 18:27             ` Dan Carpenter
2026-07-17 18:42               ` James Bottomley
2026-07-18  1:13                 ` Theodore Tso
2026-07-18  3:07                   ` James Bottomley
2026-07-17 14:54       ` Johannes Weiner
2026-07-17 16:09         ` Liam R. Howlett
2026-07-16 21:23     ` Theodore Tso
2026-07-17 13:59     ` Sasha Levin
2026-07-17 14:09       ` Konstantin Ryabitsev
2026-07-21 23:24 ` Jori Koolstra
2026-08-08  8:45 ` Dan Carpenter

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=87h5lrgxky.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=corbet@lwn.net \
    --cc=ksummit@lists.linux.dev \
    --cc=mchehab+huawei@kernel.org \
    --cc=sashal@kernel.org \
    --cc=tytso@mit.edu \
    /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