Risc-V Kvm Smstateen
Get series with b4
b4 am 20230724-scrap-pranker-7fd120078136@spudVersions newest first
- v3 Latest1 of 7 patches 0 repliesNew
1 of 7 patches is in this archive. The cover letter announces 7.
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/7 | dt-bindings: riscv: Add smstateen entry | +0 | 0 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | Conor Dooley |
|---|---|
| 2/7 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/7] Risc-V Kvm Smstateen
Hey Mayuresh,
Quoted 3 lines · Mayuresh Chitale
This series adds support to detect the Smstateen extension for both, the host and the guest vcpu. It also adds senvcfg and sstateen0 to the
ONE_REGinterface and the vcpu context save/restore.
There's not really an explanation in this series of where Smstateen is needed, or why it is only implemented for KVM. The spec mentions that this also applies to separate user threads, as well as to guests running in a hypervisor. As your first patch will lead to smstateen being set in /proc/cpuinfo, it could reasonably be assumed that the kernel itself supports the extension. Why does only KVM, and not the kernel, require support for smstateen?
Thanks,
Conor.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/kvm-riscv/attachments/20230724/412e56ab/attachment.sig>