[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da0f438bb459050e5a586a17382e961259449761.camel@intel.com>
Date: Fri, 13 May 2022 17:34:12 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"glider@...gle.com" <glider@...gle.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"hjl.tools@...il.com" <hjl.tools@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"aryabinin@...tuozzo.com" <aryabinin@...tuozzo.com>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
"x86@...nel.org" <x86@...nel.org>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Lutomirski, Andy" <luto@...nel.org>
Subject: Re: [RFCv2 03/10] x86: Introduce userspace API to handle per-thread
features
On Fri, 2022-05-13 at 16:09 +0200, Alexander Potapenko wrote:
> > +
> > + /* Handle ARCH_THREAD_FEATURE_ENABLE */
> > +
> > + task->thread.features |= features;
> > +out:
> > + return task->thread.features;
>
> Isn't arch_prctl() supposed to return 0 on success?
Hmm, good point. Maybe we'll need a struct to pass info in and out.
Powered by blists - more mailing lists