[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201207231049.GE16640@zn.tnic>
Date: Tue, 8 Dec 2020 00:10:49 +0100
From: Borislav Petkov <bp@...e.de>
To: "Bae, Chang Seok" <chang.seok.bae@...el.com>
Cc: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"mingo@...nel.org" <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"Liu, Jing2" <jing2.liu@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"luto@...nel.org" <luto@...nel.org>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
"Hansen, Dave" <dave.hansen@...el.com>,
"Brown, Len" <len.brown@...el.com>
Subject: Re: [PATCH v2 01/22] x86/fpu/xstate: Modify area init helper
prototypes to access all the possible areas
On Mon, Dec 07, 2020 at 11:03:27PM +0000, Bae, Chang Seok wrote:
> It was considered to be concise to represent, but it looks to be
> unreadable.
Not only unreadable but actively confusing - there *is* a "task" pointer
all around the kernel which we use for struct task_struct *.
> (I suspect this point applicable to PATCH2-4 as well.)
Looks like it.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
Powered by blists - more mailing lists