gregkh at linuxfoundation.org
Fri May 28 03:59:29 PDT 2021
On Fri, May 28, 2021 at 11:37:02AM +0200, Paolo Bonzini wrote:
> On 28/05/21 11:24, Greg Kroah-Hartman wrote:
> > Ok, as it sounds like this isn't going anywhere until the spec group
> > gets their work done, you all should just wait as there's no real need
> > for any kernel code here either, given that there can't be any hardware
> > made until the spec is finished anyway.
> There's need for kernel code so that userspace tooling can be built upon it.
> Not having the header files in Linus's tree makes it harder to merge RISC-V
> KVM support in userspace. KVM shields userspace from any future changes to
> the hypervisor specification; the userspace API *is* based exclusively on
> ratified specifications and there's no risk of breaking the ABI.
The "risk" is the kernel/hardware api, that seems to not be solid yet
given the spec is not released so I understand why the riscv maintainers
do not want to accept it.
Work to make that solid/released and then no one will be complaining
More information about the linux-riscv