On 2019-10-24 11:58, James Morse wrote:
Hi Shannon,
On 24/10/2019 11:27, Shannon Zhao wrote:
Curently KVM ARM64 doesn't support to compile as a kernel module.
It's
useful to compile KVM as a module.
For example, it could reload kvm without rebooting host machine.
What problem does this solve?
KVM has some funny requirements that aren't normal for a module. On
v8.0 hardware it must
have an idmap. Modules don't usually expect their code to be
physically contiguous, but
KVM does. KVM influences they way some of the irqchip stuff is set up
during early boot
(EOI mode ... not that I understand it).
We change the EOImode solely based on how we were booted (EL2 or not).
KVM doesn't directly influences that (it comes in the picture much
later).
(I think KVM-as-a-module on x86 is an artifact of how it was
developed)
This patchset support this feature while there are some limitations
to be solved. But I just send it out as RFC to get more suggestion
and
comments.
Curently it only supports for VHE system due to the hyp code section
address variables like __hyp_text_start.
We still need to support !VHE systems, and we need to do it with a
single image.
Also it can't call
kvm_update_va_mask when loading kvm module and kernel panic with
below
errors. So I make kern_hyp_va into a nop funtion.
Making this work for the single-Image on v8.0 is going to be a
tremendous amount of work.
What is the payoff?
I can only agree. !VHE is something we're going to support for the
foreseeable
future (which is roughly equivalent to "forever"), and modules have
properties
that are fundamentally incompatible with the way KVM works with !VHE.
If the only purpose of this work is to be able to swap KVM
implementations
in a development environment, then it really isn't worth the effort.
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm