public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	kvm@vger.kernel.org, Janosch Frank <frankja@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Michael Mueller <mimu@linux.vnet.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>
Subject: Re: [PATCH 1/3] s390: uv: UV feature check utility
Date: Thu, 27 Jul 2023 16:42:12 +0200	[thread overview]
Message-ID: <20230727164212.0c6cc310@p-imbrenda> (raw)
In-Reply-To: <20230727122053.774473-2-seiden@linux.ibm.com>

On Thu, 27 Jul 2023 14:20:51 +0200
Steffen Eiden <seiden@linux.ibm.com> wrote:

> Introduces a function to check the existence of an UV feature.
> Refactor feature bit checks to use the new function.
> 
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>

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

> ---
>  arch/s390/include/asm/uv.h | 5 +++++
>  arch/s390/kernel/uv.c      | 2 +-
>  arch/s390/kvm/kvm-s390.c   | 2 +-
>  arch/s390/mm/fault.c       | 2 +-
>  4 files changed, 8 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/s390/include/asm/uv.h b/arch/s390/include/asm/uv.h
> index d6bb2f4f78d1..338845402324 100644
> --- a/arch/s390/include/asm/uv.h
> +++ b/arch/s390/include/asm/uv.h
> @@ -397,6 +397,11 @@ struct uv_info {
>  
>  extern struct uv_info uv_info;
>  
> +static inline bool uv_has_feature(u8 feature_bit)
> +{
> +	return test_bit_inv(feature_bit, &uv_info.uv_feature_indications);
> +}
> +
>  #ifdef CONFIG_PROTECTED_VIRTUALIZATION_GUEST
>  extern int prot_virt_guest;
>  
> diff --git a/arch/s390/kernel/uv.c b/arch/s390/kernel/uv.c
> index d8b25cda5471..c82a667d2113 100644
> --- a/arch/s390/kernel/uv.c
> +++ b/arch/s390/kernel/uv.c
> @@ -249,7 +249,7 @@ static bool should_export_before_import(struct uv_cb_header *uvcb, struct mm_str
>  	 * shared page from a different protected VM will automatically also
>  	 * transfer its ownership.
>  	 */
> -	if (test_bit_inv(BIT_UV_FEAT_MISC, &uv_info.uv_feature_indications))
> +	if (uv_has_feature(BIT_UV_FEAT_MISC))
>  		return false;
>  	if (uvcb->cmd == UVC_CMD_UNPIN_PAGE_SHARED)
>  		return false;
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 17b81659cdb2..339e3190f6dc 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -2402,7 +2402,7 @@ static int kvm_s390_cpus_to_pv(struct kvm *kvm, u16 *rc, u16 *rrc)
>  	struct kvm_vcpu *vcpu;
>  
>  	/* Disable the GISA if the ultravisor does not support AIV. */
> -	if (!test_bit_inv(BIT_UV_FEAT_AIV, &uv_info.uv_feature_indications))
> +	if (!uv_has_feature(BIT_UV_FEAT_AIV))
>  		kvm_s390_gisa_disable(kvm);
>  
>  	kvm_for_each_vcpu(i, vcpu, kvm) {
> diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
> index b65144c392b0..b8ef42fac2c4 100644
> --- a/arch/s390/mm/fault.c
> +++ b/arch/s390/mm/fault.c
> @@ -824,7 +824,7 @@ void do_secure_storage_access(struct pt_regs *regs)
>  	 * reliable without the misc UV feature so we need to check
>  	 * for that as well.
>  	 */
> -	if (test_bit_inv(BIT_UV_FEAT_MISC, &uv_info.uv_feature_indications) &&
> +	if (uv_has_feature(BIT_UV_FEAT_MISC) &&
>  	    !test_bit_inv(61, &regs->int_parm_long)) {
>  		/*
>  		 * When this happens, userspace did something that it


  reply	other threads:[~2023-07-27 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 12:20 [PATCH 0/3] KVM: s390: Enable AP instructions for pv-guests Steffen Eiden
2023-07-27 12:20 ` [PATCH 1/3] s390: uv: UV feature check utility Steffen Eiden
2023-07-27 14:42   ` Claudio Imbrenda [this message]
2023-07-27 12:20 ` [PATCH 2/3] KVM: s390: Add UV feature negotiation Steffen Eiden
2023-07-27 15:02   ` Claudio Imbrenda
2023-07-27 12:20 ` [PATCH 3/3] KVM: s390: pv: Allow AP-instructions for pv guests Steffen Eiden
2023-07-27 15:07   ` Claudio Imbrenda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230727164212.0c6cc310@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mhartmay@linux.ibm.com \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=seiden@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox