[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ys/1pZ5Z4GlC7YEe@osiris>
Date: Thu, 14 Jul 2022 12:53:25 +0200
From: Heiko Carstens <hca@...ux.ibm.com>
To: Steffen Eiden <seiden@...ux.ibm.com>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>,
Janosch Frank <frankja@...ux.ibm.com>,
Claudio Imbrenda <imbrenda@...ux.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, nrb@...ux.ibm.com
Subject: Re: [PATCH v2 0/3] s390/cpufeature: rework to allow different types
of cpufeatures
On Wed, Jul 13, 2022 at 02:56:41PM +0200, Steffen Eiden wrote:
> Currently the s390 implementaion of cpufeature is limited to elf_hwcap
> bits. Using these to automatically load modules also exposes this
> cpufeature to userspace which, sometimes is not intended.
>
> Therefore, rework the s390-cpufeature implementation to allow for
> various cpu feature indications, which is not only limited to hwcap bits.
>
> Add a new type to allow facilities to be a cpufeature without using
> hwcap bits that expose this feature to userspace.
>
> Load uvdevice when facility 158 is present.
>
> since v1:
> * add r-bs from Claudio
> * worked in comments
>
> Heiko Carstens (2):
> s390/cpufeature: rework to allow more than only hwcap bits
> s390/cpufeature: allow for facility bits
>
> Steffen Eiden (1):
> s390/uvdevice: autoload module based on CPU facility
Series applied, thanks!
Powered by blists - more mailing lists