All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kvmarm@lists.cs.columbia.edu, maz@kernel.org,
	james.morse@arm.com, alexandru.elisei@arm.com,
	suzuki.poulose@arm.com, mark.rutland@arm.com,
	christoffer.dall@arm.com, pbonzini@redhat.com,
	drjones@redhat.com, qperret@google.com, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel-team@android.com
Subject: Re: [PATCH v3 10/15] KVM: arm64: Guest exit handlers for nVHE hyp
Date: Tue, 3 Aug 2021 16:32:22 +0100	[thread overview]
Message-ID: <20210803153222.GB31125@willie-the-truck> (raw)
In-Reply-To: <20210719160346.609914-11-tabba@google.com>

On Mon, Jul 19, 2021 at 05:03:41PM +0100, Fuad Tabba wrote:
> Add an array of pointers to handlers for various trap reasons in
> nVHE code.
> 
> The current code selects how to fixup a guest on exit based on a
> series of if/else statements. Future patches will also require
> different handling for guest exists. Create an array of handlers
> to consolidate them.
> 
> No functional change intended as the array isn't populated yet.
> 
> Acked-by: Will Deacon <will@kernel.org>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
>  arch/arm64/kvm/hyp/include/hyp/switch.h | 43 +++++++++++++++++++++++++
>  arch/arm64/kvm/hyp/nvhe/switch.c        | 35 ++++++++++++++++++++
>  2 files changed, 78 insertions(+)

Definitely keep my Ack on this, but Clang just chucked out a warning due to:

> diff --git a/arch/arm64/kvm/hyp/include/hyp/switch.h b/arch/arm64/kvm/hyp/include/hyp/switch.h
> index a0e78a6027be..5a2b89b96c67 100644
> --- a/arch/arm64/kvm/hyp/include/hyp/switch.h
> +++ b/arch/arm64/kvm/hyp/include/hyp/switch.h
> @@ -409,6 +409,46 @@ static inline bool __hyp_handle_ptrauth(struct kvm_vcpu *vcpu)
>  	return true;
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);
> +
> +exit_handle_fn kvm_get_nvhe_exit_handler(struct kvm_vcpu *vcpu);

and:

> diff --git a/arch/arm64/kvm/hyp/nvhe/switch.c b/arch/arm64/kvm/hyp/nvhe/switch.c
> index 86f3d6482935..36da423006bd 100644
> --- a/arch/arm64/kvm/hyp/nvhe/switch.c
> +++ b/arch/arm64/kvm/hyp/nvhe/switch.c
> @@ -158,6 +158,41 @@ static void __pmu_switch_to_host(struct kvm_cpu_context *host_ctxt)
>  		write_sysreg(pmu->events_host, pmcntenset_el0);
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);

Which leads to:

arch/arm64/kvm/hyp/nvhe/switch.c:189:15: warning: redefinition of typedef 'exit_handle_fn' is a C11 feature [-Wtypedef-redefinition]
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
./arch/arm64/kvm/hyp/include/hyp/switch.h:416:15: note: previous definition is here
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
1 warning generated.

So I guess just pick your favourite?

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kernel-team@android.com, kvm@vger.kernel.org, maz@kernel.org,
	pbonzini@redhat.com, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 10/15] KVM: arm64: Guest exit handlers for nVHE hyp
Date: Tue, 3 Aug 2021 16:32:22 +0100	[thread overview]
Message-ID: <20210803153222.GB31125@willie-the-truck> (raw)
In-Reply-To: <20210719160346.609914-11-tabba@google.com>

On Mon, Jul 19, 2021 at 05:03:41PM +0100, Fuad Tabba wrote:
> Add an array of pointers to handlers for various trap reasons in
> nVHE code.
> 
> The current code selects how to fixup a guest on exit based on a
> series of if/else statements. Future patches will also require
> different handling for guest exists. Create an array of handlers
> to consolidate them.
> 
> No functional change intended as the array isn't populated yet.
> 
> Acked-by: Will Deacon <will@kernel.org>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
>  arch/arm64/kvm/hyp/include/hyp/switch.h | 43 +++++++++++++++++++++++++
>  arch/arm64/kvm/hyp/nvhe/switch.c        | 35 ++++++++++++++++++++
>  2 files changed, 78 insertions(+)

Definitely keep my Ack on this, but Clang just chucked out a warning due to:

> diff --git a/arch/arm64/kvm/hyp/include/hyp/switch.h b/arch/arm64/kvm/hyp/include/hyp/switch.h
> index a0e78a6027be..5a2b89b96c67 100644
> --- a/arch/arm64/kvm/hyp/include/hyp/switch.h
> +++ b/arch/arm64/kvm/hyp/include/hyp/switch.h
> @@ -409,6 +409,46 @@ static inline bool __hyp_handle_ptrauth(struct kvm_vcpu *vcpu)
>  	return true;
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);
> +
> +exit_handle_fn kvm_get_nvhe_exit_handler(struct kvm_vcpu *vcpu);

and:

> diff --git a/arch/arm64/kvm/hyp/nvhe/switch.c b/arch/arm64/kvm/hyp/nvhe/switch.c
> index 86f3d6482935..36da423006bd 100644
> --- a/arch/arm64/kvm/hyp/nvhe/switch.c
> +++ b/arch/arm64/kvm/hyp/nvhe/switch.c
> @@ -158,6 +158,41 @@ static void __pmu_switch_to_host(struct kvm_cpu_context *host_ctxt)
>  		write_sysreg(pmu->events_host, pmcntenset_el0);
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);

Which leads to:

arch/arm64/kvm/hyp/nvhe/switch.c:189:15: warning: redefinition of typedef 'exit_handle_fn' is a C11 feature [-Wtypedef-redefinition]
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
./arch/arm64/kvm/hyp/include/hyp/switch.h:416:15: note: previous definition is here
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
1 warning generated.

So I guess just pick your favourite?

Will
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kvmarm@lists.cs.columbia.edu, maz@kernel.org,
	james.morse@arm.com, alexandru.elisei@arm.com,
	suzuki.poulose@arm.com, mark.rutland@arm.com,
	christoffer.dall@arm.com, pbonzini@redhat.com,
	drjones@redhat.com, qperret@google.com, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kernel-team@android.com
Subject: Re: [PATCH v3 10/15] KVM: arm64: Guest exit handlers for nVHE hyp
Date: Tue, 3 Aug 2021 16:32:22 +0100	[thread overview]
Message-ID: <20210803153222.GB31125@willie-the-truck> (raw)
In-Reply-To: <20210719160346.609914-11-tabba@google.com>

On Mon, Jul 19, 2021 at 05:03:41PM +0100, Fuad Tabba wrote:
> Add an array of pointers to handlers for various trap reasons in
> nVHE code.
> 
> The current code selects how to fixup a guest on exit based on a
> series of if/else statements. Future patches will also require
> different handling for guest exists. Create an array of handlers
> to consolidate them.
> 
> No functional change intended as the array isn't populated yet.
> 
> Acked-by: Will Deacon <will@kernel.org>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
>  arch/arm64/kvm/hyp/include/hyp/switch.h | 43 +++++++++++++++++++++++++
>  arch/arm64/kvm/hyp/nvhe/switch.c        | 35 ++++++++++++++++++++
>  2 files changed, 78 insertions(+)

Definitely keep my Ack on this, but Clang just chucked out a warning due to:

> diff --git a/arch/arm64/kvm/hyp/include/hyp/switch.h b/arch/arm64/kvm/hyp/include/hyp/switch.h
> index a0e78a6027be..5a2b89b96c67 100644
> --- a/arch/arm64/kvm/hyp/include/hyp/switch.h
> +++ b/arch/arm64/kvm/hyp/include/hyp/switch.h
> @@ -409,6 +409,46 @@ static inline bool __hyp_handle_ptrauth(struct kvm_vcpu *vcpu)
>  	return true;
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);
> +
> +exit_handle_fn kvm_get_nvhe_exit_handler(struct kvm_vcpu *vcpu);

and:

> diff --git a/arch/arm64/kvm/hyp/nvhe/switch.c b/arch/arm64/kvm/hyp/nvhe/switch.c
> index 86f3d6482935..36da423006bd 100644
> --- a/arch/arm64/kvm/hyp/nvhe/switch.c
> +++ b/arch/arm64/kvm/hyp/nvhe/switch.c
> @@ -158,6 +158,41 @@ static void __pmu_switch_to_host(struct kvm_cpu_context *host_ctxt)
>  		write_sysreg(pmu->events_host, pmcntenset_el0);
>  }
>  
> +typedef int (*exit_handle_fn)(struct kvm_vcpu *);

Which leads to:

arch/arm64/kvm/hyp/nvhe/switch.c:189:15: warning: redefinition of typedef 'exit_handle_fn' is a C11 feature [-Wtypedef-redefinition]
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
./arch/arm64/kvm/hyp/include/hyp/switch.h:416:15: note: previous definition is here
typedef int (*exit_handle_fn)(struct kvm_vcpu *);
              ^
1 warning generated.

So I guess just pick your favourite?

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-08-03 15:32 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 16:03 [PATCH v3 00/15] KVM: arm64: Fixed features for protected VMs Fuad Tabba
2021-07-19 16:03 ` Fuad Tabba
2021-07-19 16:03 ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 01/15] KVM: arm64: placeholder to check if VM is protected Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  8:58   ` Will Deacon
2021-08-12  8:58     ` Will Deacon
2021-08-12  8:58     ` Will Deacon
2021-08-12  9:22     ` Fuad Tabba
2021-08-12  9:22       ` Fuad Tabba
2021-08-12  9:22       ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 02/15] KVM: arm64: Remove trailing whitespace in comment Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  8:59   ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 03/15] KVM: arm64: MDCR_EL2 is a 64-bit register Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 04/15] KVM: arm64: Fix names of config register fields Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h,c for nVHE reuse Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-20 13:38   ` Andrew Jones
2021-07-20 13:38     ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h, c " Andrew Jones
2021-07-20 13:38     ` Andrew Jones
2021-07-20 14:03     ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h,c " Fuad Tabba
2021-07-20 14:03       ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h, c " Fuad Tabba
2021-07-20 14:03       ` Fuad Tabba
2021-08-12  8:59   ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h,c " Will Deacon
2021-08-12  8:59     ` [PATCH v3 05/15] KVM: arm64: Refactor sys_regs.h, c " Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 06/15] KVM: arm64: Restore mdcr_el2 from vcpu Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-20 14:52   ` Andrew Jones
2021-07-20 14:52     ` Andrew Jones
2021-07-20 14:52     ` Andrew Jones
2021-07-21  7:37     ` Fuad Tabba
2021-07-21  7:37       ` Fuad Tabba
2021-07-21  7:37       ` Fuad Tabba
2021-08-12  8:46       ` Will Deacon
2021-08-12  8:46         ` Will Deacon
2021-08-12  8:46         ` Will Deacon
2021-08-12  9:28         ` Fuad Tabba
2021-08-12  9:28           ` Fuad Tabba
2021-08-12  9:28           ` Fuad Tabba
2021-08-12  9:49           ` Will Deacon
2021-08-12  9:49             ` Will Deacon
2021-08-12  9:49             ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 07/15] KVM: arm64: Track value of cptr_el2 in struct kvm_vcpu_arch Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  8:59   ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 08/15] KVM: arm64: Add feature register flag definitions Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  8:59   ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-08-12  9:21     ` Fuad Tabba
2021-08-12  9:21       ` Fuad Tabba
2021-08-12  9:21       ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 09/15] KVM: arm64: Add config register bit definitions Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  8:59   ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-08-12  8:59     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 10/15] KVM: arm64: Guest exit handlers for nVHE hyp Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-03 15:32   ` Will Deacon [this message]
2021-08-03 15:32     ` Will Deacon
2021-08-03 15:32     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 11/15] KVM: arm64: Add trap handlers for protected VMs Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  9:45   ` Will Deacon
2021-08-12  9:45     ` Will Deacon
2021-08-12  9:45     ` Will Deacon
2021-08-16 14:39     ` Fuad Tabba
2021-08-16 14:39       ` Fuad Tabba
2021-08-16 14:39       ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 12/15] KVM: arm64: Move sanitized copies of CPU features Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  9:46   ` Will Deacon
2021-08-12  9:46     ` Will Deacon
2021-08-12  9:46     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 13/15] KVM: arm64: Trap access to pVM restricted features Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  9:53   ` Will Deacon
2021-08-12  9:53     ` Will Deacon
2021-08-12  9:53     ` Will Deacon
2021-07-19 16:03 ` [PATCH v3 14/15] KVM: arm64: Handle protected guests at 32 bits Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 19:43   ` Oliver Upton
2021-07-19 19:43     ` Oliver Upton
2021-07-19 19:43     ` Oliver Upton
2021-07-21  8:39     ` Fuad Tabba
2021-07-21  8:39       ` Fuad Tabba
2021-07-21  8:39       ` Fuad Tabba
2021-08-12  9:57   ` Will Deacon
2021-08-12  9:57     ` Will Deacon
2021-08-12  9:57     ` Will Deacon
2021-08-12 13:08     ` Fuad Tabba
2021-08-12 13:08       ` Fuad Tabba
2021-08-12 13:08       ` Fuad Tabba
2021-07-19 16:03 ` [PATCH v3 15/15] KVM: arm64: Restrict protected VM capabilities Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-07-19 16:03   ` Fuad Tabba
2021-08-12  9:59   ` Will Deacon
2021-08-12  9:59     ` Will Deacon
2021-08-12  9:59     ` Will Deacon
2021-08-16 14:40     ` Fuad Tabba
2021-08-16 14:40       ` Fuad Tabba
2021-08-16 14:40       ` Fuad Tabba

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=20210803153222.GB31125@willie-the-truck \
    --to=will@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=drjones@redhat.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qperret@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.