Closed jglathe closed 10 months ago
Hi @jglathe,
The series should apply on https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20231215
Thanks. Do I have a chance to actually load the gunyah hypervisor on QCOM hardware? Or is the testable use case qemu on x86-host only?
For now this release only supports qemu on x86 host only. We still didn't release the files/support required for QCom platform. In future we are planning to add support for additional platforms (TBD).
Like sc8280xp based devices? 😼
May be one of our future dragonboards, its not confirmed which one yet.
Looks like the latest version of the patches do not support crosvm. So we need to prevent from applying these latest patches. We need to specify the version to pick. Following seems to work.
-${LINUX_DIR}/tools/b4/b4.sh shazam https://lore.kernel.org/all/20230613172054.3959700-1-quic_eberman@quicinc.com/ +${LINUX_DIR}/tools/b4/b4.sh shazam -v 14 https://lore.kernel.org/all/20230613172054.3959700-1-quic_eberman@quicinc.com/
One finding regarding patchset v15: To build these drivers as modules (which is allowed according to Kconfig) you need an additional export for anon_inode_getfile_secure.
Just noticed while preparing a new round of tests:
shazam appears to grab the newest available patchset, lore.kernel.org/all/20231215-gunyah-v15-0-192a5d872a30@quicinc.com which is not entirely compatible with this kernel (6.5?). I have applied the same patchset in my kernel (6.7-rc6), and I needed some tweaks to account for some other refactorings that were done.