[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <368CA4A7-3640-45F7-810F-2E2A073FE27C@oracle.com>
Date: Wed, 12 Nov 2025 23:17:41 +0000
From: Prakash Sangappa <prakash.sangappa@...cle.com>
To: Thomas Gleixner <tglx@...utronix.de>
CC: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
LKML
<linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Paul
E. McKenney" <paulmck@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Jonathan Corbet <corbet@....net>,
Madadi Vineeth Reddy
<vineethr@...ux.ibm.com>,
K Prateek Nayak <kprateek.nayak@....com>,
Steven
Rostedt <rostedt@...dmis.org>,
Sebastian Andrzej Siewior
<bigeasy@...utronix.de>,
Arnd Bergmann <arnd@...db.de>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: [patch V3 00/12] rseq: Implement time slice extension mechanism
> On Nov 12, 2025, at 1:57 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Wed, Nov 12 2025 at 06:30, Prakash Sangappa wrote:
>> The problem reproduces on a 2 socket AMD(384 cpus) bare metal system.
>> It occurs soon after system boot up. Does not reproduce on a 64cpu VM.
>
> Can you verify that the top most commit of the rseq/slice branch is:
>
> d2eb5c9c0693 ("selftests/rseq: Implement time slice extension test")
No it is
c46f12a1166058764da8e84a215a6b66cae2fe0a
selftests/rseq: Implement time slice extension test
I can refresh and try.
-Prakash
>
> Thanks,
>
> tglx
Powered by blists - more mailing lists