mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: will@kernel.org, Xiaofei Tan <tanxiaofei@huawei.com>,
	Dave.Martin@arm.com, catalin.marinas@arm.com, broonie@kernel.org,
	julien.grall@arm.com
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linuxarm@openeuler.org
Subject: Re: [PATCH RFC for-next 1/1] arm64: sve: Fix some compile errors about sve_cond_update_zcr_vq
Date: Wed, 31 Mar 2021 11:09:50 +0100	[thread overview]
Message-ID: <161718535763.4004332.2029416282173355832.b4-ty@kernel.org> (raw)
In-Reply-To: <1617183879-48748-1-git-send-email-tanxiaofei@huawei.com>

On Wed, 31 Mar 2021 17:44:39 +0800, Xiaofei Tan wrote:
> There are some compile errors of ARM64 KVM when ARM64_SVE is not
> selected, in the locations of sve_cond_update_zcr_vq used.
> One error log is as following:
> 
>   CC      arch/arm64/kvm/sys_regs.o
> In file included from arch/arm64/kvm/hyp/vhe/switch.c:8:0:
> ./arch/arm64/kvm/hyp/include/hyp/switch.h: In function ‘__hyp_sve_restore_guest’:
> ./arch/arm64/kvm/hyp/include/hyp/switch.h:220:2: error: implicit declaration of
> function ‘sve_cond_update_zcr_vq’; did you mean
> ‘kvm_pmu_update_run’? [-Werror=implicit-function-declaration]
>   sve_cond_update_zcr_vq(vcpu_sve_max_vq(vcpu) - 1, SYS_ZCR_EL2);
>   ^~~~~~~~~~~~~~~~~~~~~~
>   kvm_pmu_update_run
> 
> [...]

Applied to kvm-arm64/nvhe-sve, thanks!

[1/1] arm64: sve: Fix some compile errors about sve_cond_update_zcr_vq
      commit: a9f8696d4be5228de9d1d4f0e9f027b64d77dab6

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.



      reply	other threads:[~2021-03-31 10:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  9:44 Xiaofei Tan
2021-03-31 10:09 ` Marc Zyngier [this message]

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=161718535763.4004332.2029416282173355832.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=julien.grall@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=tanxiaofei@huawei.com \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®