ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The role of AI and LLMs in the kernel process
Date: Tue, 05 Aug 2025 13:23:18 -0400	[thread overview]
Message-ID: <e9902e53cd5c8ad444d6c62942e790b7ba5d756a.camel@HansenPartnership.com> (raw)
In-Reply-To: <ad8ea0a6-ca53-47f8-92ec-17e970184019@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]

On Tue, 2025-08-05 at 18:11 +0100, Mark Brown wrote:
> On Tue, Aug 05, 2025 at 12:43:38PM -0400, James Bottomley wrote:
> > On Tue, 2025-08-05 at 17:03 +0100, Lorenzo Stoakes wrote:
> 
> > > * On the other hand, there are use cases which are useful - test
> > > data/code generation, summarisation, smart auto-complete - so
> > > it'd perhaps be foolish to entirely dismiss AI.
> 
> > Patch backporting is another such nice use.
> 
> Patch backporting sounds pretty scary to me, it's the sort of thing
> where extra context that needs to be accounted for is very likely to
> come up (eg, assumptions you can make about existing state or
> santisation).

If you think about it, the git history contains the exact patch path
between where the patch was applied and where you want to apply it. 
That's a finite data set which LLMs can be trained to work nicely with.

>   That trips up humans often enough and doesn't seem like it's
> playing to the strengths advertised for LLMs.

Humans don't look at the patch path (or use something broad like a
range scan).  The AI can be patient enough to actually go over it all.

> TBH I'm not thrilled about the general test code is trivial
> assumption either,

I don't think anyone who trains AI thinks testing is trivial.  It does
take special training for AI to be good at test writing.

>  unstable test code or test code that doesn't cover what people think
> it covers are both problems.

Test coverage and constructing tests for coverage is another place AI
can help.  Especially given coverage is a measurable quantity which
makes training easier.

>   The issues when things go wrong are less severe than the kernel
> itself but things still need to be maintained and we already have
> issues with people being dismissive of the selftests.

Well our selftests, having just spent ages figuring out how to run a
subset of the bpf tests, are very eccentric ... in that each test set
runs in a completely different way from any of the others and knowledge
from one selftest area doesn't apply to a different one.

Regards,

James


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-05 17:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 16:03 Lorenzo Stoakes
2025-08-05 16:43 ` James Bottomley
2025-08-05 17:11   ` Mark Brown
2025-08-05 17:23     ` James Bottomley [this message]
2025-08-05 17:43       ` Sasha Levin
2025-08-05 17:58         ` Lorenzo Stoakes
2025-08-05 18:16       ` Mark Brown
2025-08-05 18:01     ` Lorenzo Stoakes
2025-08-05 18:46       ` Mark Brown
2025-08-05 19:18         ` Lorenzo Stoakes
2025-08-05 17:17   ` Stephen Hemminger
2025-08-05 17:55   ` Lorenzo Stoakes
2025-08-05 18:23     ` Lorenzo Stoakes
2025-08-12 13:44       ` Steven Rostedt
2025-08-05 18:34     ` James Bottomley
2025-08-05 18:55       ` Lorenzo Stoakes
2025-08-12 13:50       ` Steven Rostedt
2025-08-05 18:39     ` Sasha Levin
2025-08-05 19:15       ` Lorenzo Stoakes
2025-08-05 20:02         ` James Bottomley
2025-08-05 20:48           ` Al Viro
2025-08-06 19:26           ` Lorenzo Stoakes
2025-08-07 12:25             ` Mark Brown
2025-08-07 13:00               ` Lorenzo Stoakes
2025-08-11 21:26                 ` Luis Chamberlain
2025-08-12 14:19                 ` Steven Rostedt
2025-08-06  4:04       ` Alexey Dobriyan
2025-08-06 20:36         ` Sasha Levin
2025-08-05 21:58   ` Jiri Kosina
2025-08-06  6:58     ` Hannes Reinecke
2025-08-06 19:36       ` Lorenzo Stoakes
2025-08-06 19:35     ` Lorenzo Stoakes
2025-08-05 18:10 ` H. Peter Anvin
2025-08-05 18:19   ` Lorenzo Stoakes
2025-08-06  5:49   ` Julia Lawall
2025-08-06  9:25     ` Dan Carpenter
2025-08-06  9:39       ` Julia Lawall
2025-08-06 19:30       ` Lorenzo Stoakes
2025-08-12 14:37         ` Steven Rostedt
2025-08-12 15:02           ` Sasha Levin
2025-08-12 15:24             ` Paul E. McKenney
2025-08-12 15:25               ` Sasha Levin
2025-08-12 15:28                 ` Paul E. McKenney

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=e9902e53cd5c8ad444d6c62942e790b7ba5d756a.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=broonie@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox