[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9086a511-bd3e-4a88-ad86-8c51d5a385ac@gmail.com>
Date: Sun, 11 May 2025 22:04:46 +0200
From: Christian Lamparter <chunkeey@...il.com>
To: Johannes Berg <johannes@...solutions.net>, linux-kernel@...r.kernel.org,
linux-um@...ts.infradead.org
Cc: benjamin.berg@...el.com, sashal@...nel.org, richard@....at,
stable@...r.kernel.org
Subject: Re: [PATCH 6.12] Revert "um: work around sched_yield not yielding in
time-travel mode"
On 5/11/25 9:23 PM, Johannes Berg wrote:
> On Fri, 2025-05-09 at 11:50 +0200, Christian Lamparter wrote:
>>
>> What's interesting/very strange strange about this time-travel stuff:
>>> commit 0b8b2668f998 ("um: insert scheduler ticks when userspace does not yield")
>>
>> $ git describe 0b8b2668f998
>> => v6.12-rc2-43-g0b8b2668f998
>>
>
> Come to think of it, often you just want "git describe --contains":
>
> $ git describe --contains --match=v* 0b8b2668f998
> v6.13-rc1~18^2~25
yeah, I'm wondering if this 'git describe vs git describe --contains' could be the
reason why the patch was AUTOSEL'd? I have no idea how Sasha's helper works though.
As for UML: Your work is greatly appreciated. I've ran into this because OpenWrt is
currently in the process of adapting to the 6.12 LTS:
https://github.com/openwrt/openwrt/pull/18666
Cheers,
Christian
Powered by blists - more mailing lists