From: kernel test robot <lkp@intel.com>
To: Will Deacon <will@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Ard Biesheuvel <ardb@google.com>
Subject: [sudeep-holla:android13-5.15/ffa 2786/4062] arch/arm64/kvm/arm.c:2011:39: error: use of undeclared identifier 'smccc_trng_available'
Date: Sat, 10 Feb 2024 12:48:04 +0800 [thread overview]
Message-ID: <202402101209.a7Y2FFcM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git android13-5.15/ffa
head: c6013f50f1ae0e42d14d51a06118779ead3047ef
commit: 888643ea37b504cb32afdd6430698d1e92a79a71 [2786/4062] ANDROID: KVM: arm64: relay entropy requests from protected guests directly to secure
config: arm64-randconfig-r063-20240209 (https://download.01.org/0day-ci/archive/20240210/202402101209.a7Y2FFcM-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project ac0577177f053ba7e7016e1b7e44cf5932d00b03)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240210/202402101209.a7Y2FFcM-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202402101209.a7Y2FFcM-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/arm64/kvm/arm.c:2011:39: error: use of undeclared identifier 'smccc_trng_available'
2011 | kvm_nvhe_sym(smccc_trng_available) = smccc_trng_available;
| ^
1 error generated.
vim +/smccc_trng_available +2011 arch/arm64/kvm/arm.c
1997
1998 static int kvm_hyp_init_protection(u32 hyp_va_bits)
1999 {
2000 void *addr = phys_to_virt(hyp_mem_base);
2001 int ret;
2002
2003 kvm_nvhe_sym(id_aa64pfr0_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64PFR0_EL1);
2004 kvm_nvhe_sym(id_aa64pfr1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64PFR1_EL1);
2005 kvm_nvhe_sym(id_aa64isar0_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64ISAR0_EL1);
2006 kvm_nvhe_sym(id_aa64isar1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64ISAR1_EL1);
2007 kvm_nvhe_sym(id_aa64mmfr0_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR0_EL1);
2008 kvm_nvhe_sym(id_aa64mmfr1_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR1_EL1);
2009 kvm_nvhe_sym(id_aa64mmfr2_el1_sys_val) = read_sanitised_ftr_reg(SYS_ID_AA64MMFR2_EL1);
2010 kvm_nvhe_sym(__icache_flags) = __icache_flags;
> 2011 kvm_nvhe_sym(smccc_trng_available) = smccc_trng_available;
2012
2013 ret = create_hyp_mappings(addr, addr + hyp_mem_size, PAGE_HYP);
2014 if (ret)
2015 return ret;
2016
2017 ret = init_stage2_iommu();
2018 if (ret < 0)
2019 return ret;
2020
2021 ret = do_pkvm_init(hyp_va_bits, (enum kvm_iommu_driver)ret);
2022 if (ret)
2023 return ret;
2024
2025 free_hyp_pgds();
2026
2027 return 0;
2028 }
2029
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-10 4:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202402101209.a7Y2FFcM-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.