[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0044b843e959e7b32f9da7b58469f6685c9b2d13.camel@intel.com>
Date: Tue, 25 Jun 2024 13:45:40 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "mingo@...nel.org" <mingo@...nel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "bp@...en8.de"
<bp@...en8.de>, "peterz@...radead.org" <peterz@...radead.org>,
"hpa@...or.com" <hpa@...or.com>, "luto@...capital.net" <luto@...capital.net>,
"tglx@...utronix.de" <tglx@...utronix.de>, "torvalds@...ux-foundation.org"
<torvalds@...ux-foundation.org>, "dave@...1.net" <dave@...1.net>,
"oleg@...hat.com" <oleg@...hat.com>, "ubizjak@...il.com" <ubizjak@...il.com>
Subject: Re: [PATCH 2/3] x86/fpu: Remove the thread::fpu pointer
On Mon, 2024-06-24 at 22:26 -0700, Rick Edgecombe wrote:
>
> If it's not obvious, I can investigate some more tomorrow on a more normal VM
> configuration.
I see the same issue on a normal VM. CONFIG_DEBUG_LOCK_ALLOC seems to be the
critical config.
Powered by blists - more mailing lists