linux-kernel - Re: [PATCH 2/3] s390/cpufeature: allow for facility bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 12 Jul 2022 18:50:13 +0200
From:   Claudio Imbrenda <imbrenda@...ux.ibm.com>
To:     Steffen Eiden <seiden@...ux.ibm.com>
Cc:     Heiko Carstens <hca@...ux.ibm.com>,
        Alexander Gordeev <agordeev@...ux.ibm.com>,
        Christian Borntraeger <borntraeger@...ux.ibm.com>,
        Janosch Frank <frankja@...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 2/3] s390/cpufeature: allow for facility bits

On Tue, 12 Jul 2022 12:52:19 +0200
Steffen Eiden <seiden@...ux.ibm.com> wrote:

> From: Heiko Carstens <hca@...ux.ibm.com>
> 
> Allow for facility bits to be used in cpu features.
> 
> Signed-off-by: Heiko Carstens <hca@...ux.ibm.com>

Reviewed-by: Claudio Imbrenda <imbrenda@...ux.ibm.com>

> ---
>  arch/s390/kernel/cpufeature.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/arch/s390/kernel/cpufeature.c b/arch/s390/kernel/cpufeature.c
> index ea4bbfd855db..e70b29804db4 100644
> --- a/arch/s390/kernel/cpufeature.c
> +++ b/arch/s390/kernel/cpufeature.c
> @@ -10,6 +10,7 @@
>  
>  enum {
>  	TYPE_HWCAP,
> +	TYPE_FACILITY,
>  };
>  
>  struct s390_cpu_feature {
> @@ -54,6 +55,8 @@ int cpu_have_feature(unsigned int num)
>  	switch (feature->type) {
>  	case TYPE_HWCAP:
>  		return !!(elf_hwcap & (1UL << feature->num));
> +	case TYPE_FACILITY:
> +		return test_facility(feature->num);
>  	default:
>  		WARN_ON_ONCE(1);
>  		return 0;