get_flat_ccs_offset() reads the base of the flat CCS storage from the
hardware, scales it by the number of enabled L3 nodes, and rounds the
result up to 128K. Everything below that offset is then ...
If an AI can find the bug and point it out, I don’t see a problem, as long as it is checked thoroughly enough by an actual skilled programmer, to make sure that doing what the AI suggest is not making things worse.
And this was a debug session from hell, enormously helped by an AI
doing much of the grunt-work.
I’d like to call it my tireless helper, but the AI several times
stated flat out that this was impossible and unsolvable and that we
should just write a report about it.
I suspect those things have been trained by people who may not be
quite as stubborn as I am.
But while the AI was ready to give up several times, it did keep
adding debug code and analyzing it faithfully when I pushed. So credit
where credit is due and I let the AI write the commit message above.
This is basically a one-liner fixing a bogus “round_up()” to a
“round_down()”, but there were 24 patches adding more and more debug
information to this, and 18 kernel boot to finally narrow it down to
this. - Linus
That’s a long way short of finding the bug and pointing it out, and instead is just the tedious work of adding checks and then deciding where to add more checks when you have the result of the previous checks. I suspect if we’d spent a trillion dollars on a tool for that, we could have come up with something much more efficient than an LLM.
I have found that LLM agents can monitor ALL the logs, synthesize information that takes me hours to put together in minutes - and when there’s a problem in there it can spot it faster and more often than me. It can also miss things, not as many as I miss given equal time to work the problem, but it’s not perfect - just better. Like cutting down a tree with a chainsaw, instead of a bare hacksaw blade.
“who may not be quite as stubborn as I am” that is the most Linus torvalds thing to say. good to see his passive agressive nature being put in a press release.
If an AI can find the bug and point it out, I don’t see a problem, as long as it is checked thoroughly enough by an actual skilled programmer, to make sure that doing what the AI suggest is not making things worse.
The exact quote is:
That’s a long way short of finding the bug and pointing it out, and instead is just the tedious work of adding checks and then deciding where to add more checks when you have the result of the previous checks. I suspect if we’d spent a trillion dollars on a tool for that, we could have come up with something much more efficient than an LLM.
I have found that LLM agents can monitor ALL the logs, synthesize information that takes me hours to put together in minutes - and when there’s a problem in there it can spot it faster and more often than me. It can also miss things, not as many as I miss given equal time to work the problem, but it’s not perfect - just better. Like cutting down a tree with a chainsaw, instead of a bare hacksaw blade.
“who may not be quite as stubborn as I am” that is the most Linus torvalds thing to say. good to see his passive agressive nature being put in a press release.
Press release? This is a github commit.
You must be an ex reddit user as you neither clicked the link, nor looked at the domain it linked to.
Just a nitpick, git commit. Kernel development has nothing to do with GitHub other than the fact that there is a mirror of the repo in there.
You will be surprised to know, “ex-reddit user” is the majority of Lemmy users.
But most of us have the decency to be ashamed about it.
why? reddit actually had content and debate
It’s not that serious