All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Chris Mason <mason@kernel.org>,
	sashiko@lists.linux.dev,
	Roman Gushchin <roman.gushchin@linux.dev>,
	ast@kernel.org, kuba@kernel.org
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: [RFC] reworking the review-prompts subsystem guide
Date: Fri, 23 Oct 2026 12:27:42 -0700	[thread overview]
Message-ID: <69794757-5b55-4796-8388-35a074842708@linux.dev> (raw)
In-Reply-To: <f8295279-7af7-4b3e-bc9b-112bfc49816b@linux.dev>

On 10/6/26 2:22 PM, Ihor Solodrai wrote:
> On 10/2/26 12:04 PM, Chris Mason wrote:
>> Hi everyone,
>>
>> I've been updating the review prompts, and you can find my current work here in the subsystem-build branch:
>>
>> https://github.com/masoncl/review-prompts.git subsystem-build
> 
> Hi Chris,
> 
> I've set up "shadow" AI reviews for BPF, taking advantage of our
> existing bpf-rc infra. It's a copy of the entire BPF CI pipeline that
> we occasionally use for testing of the CI itself.
> 
> [...]
> 
> I just pushed, it'll take a few days before we get any real samples.

Hi all.

Got results from a couple of weeks of running the subsystem-build
branch prompts on bpf list: 272 patches in 50 series total.

TL;DR: BPF bot will switch to the subsystem-build prompts. There are
no regressions in findings, and overall the results are quite similar.

Chris, IMO you can just merge subsystem-build into main.

Some stats:
  * Same outcome (review posted vs clean) on 90% of commits.
  * Medium/high issues: posted on 7.4% of commits, vs 5.9% before.
  * Low/nit-only reviews: 10.3% of commits, vs 15.8% before.
  * Cost +6%, same wall time.

Interesting findings:
  * Old vs new prompts differ about as much as two runs of the old
    prompts do: on an unchanged patch reposted in the next version,
    production reproduces only about half of its own findings.
  * The new guides are consulted in every review, but only 3 of 114
    new findings cite a guide answer, and the old prompts found those
    too. No clear wins attributable to the guides yet.
  * The new prompts no longer produce the "A subsystem pattern flags
    this as potentially concerning" items (mostly selftests style).

Overall, it appears that prompts tuning becomes less important vs base
model improvements, at least in the context of searching for
regressions on patches. As long as the core intent is expressed in the
"root" prompts.

The analysis was done by AI, of course, so grains of salt everywhere.

If anyone's interested I can share the dataset and analysis details
separately. Let me know.

Thanks.

> 
> Thank you for working on the prompts!
> 
>>
>> [...]


  parent reply	other threads:[~2026-10-23 19:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 19:04 [RFC] reworking the review-prompts subsystem guide Chris Mason
2026-10-02 21:18 ` Chuck Lever
2026-10-04  9:17   ` Chris Mason
2026-10-05 19:58 ` Jakub Kicinski
2026-10-05 21:14   ` Roman Gushchin
2026-10-05 21:53     ` Jakub Kicinski
2026-10-05 23:37     ` Ihor Solodrai
2026-10-06 21:22 ` Ihor Solodrai
2026-10-07  9:00   ` Chris Mason
2026-10-23 19:27   ` Ihor Solodrai [this message]
2026-10-23 20:22     ` Roman Gushchin
2026-10-23 21:26       ` Ihor Solodrai
2026-10-09 14:17 ` Fuad Tabba
2026-10-09 17:57   ` Chris Mason
2026-10-10 15:53     ` Fuad Tabba
2026-10-12 15:14       ` Fuad Tabba

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=69794757-5b55-4796-8388-35a074842708@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=mason@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko@lists.linux.dev \
    /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.