|
|
Log in / Subscribe / Register

Why RISC-V doesn't (yet) support KVM

Why RISC-V doesn't (yet) support KVM

Posted May 22, 2021 16:37 UTC (Sat) by mfuzzey (subscriber, #57966)
In reply to: Why RISC-V doesn't (yet) support KVM by pwsan
Parent article: Why RISC-V doesn't (yet) support KVM

Is it shipping *systems* or *chips* that don't exist yet?
Presumably those developing this feature are testing it on something.

If the chips exist just no one is selling systems with them yet (presumably the developers having custom prototype boards) then I see no reason not to merge the feature as the chips aren't going to change.

OTOH if no chips exist yet (eg if prototyping is being done on a FPGA) I can see the rational for waiting if there is a real risk that the final hardware is different.
But even in this case does it really matter given that the user space won't be affected? Sure the kernel code may have to change for the final hardware but if the prototype hardware never shipped does this matter as there will be no need to support both in the kernel.

I may be missing something obvious here as I'm not well versed in RISC V


to post comments

Why RISC-V doesn't (yet) support KVM

Posted May 23, 2021 7:44 UTC (Sun) by ssmith32 (subscriber, #72404) [Link]

I think this was the argument being made here:

"In fact, quite a few people have already implemented RISC-V H-extension in hardware as well and KVM RISC-V works on real HW as well. "

And which sounds like the main reason it may end up being merged into stg.

Why RISC-V doesn't (yet) support KVM

Posted May 26, 2021 0:29 UTC (Wed) by pwsan (guest, #56604) [Link]

> Presumably those developing this feature are testing it on something.

Probably most people are using QEMU to experiment with this, with the instructions and code here:

https://github.com/kvm-riscv


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds