RFC Making KVM_GET_ONE_REG/KVM_SET_ONE_REG generic.
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 42 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | KVM: Move KVM_SET_ONE_REG/KVM_GET_ONE_REG to generic code.arch/ arch/ arch/ +6 more | +35 | 3 replies | |
| 2/5 | KVM: ARM: use KVM_SET_ONE_REG/KVM_GET_ONE_REG.arch/ arch/ arch/ +2 more | +103 | 1 reply | |
| 3/5 | KVM: Add KVM_VCPU_GET_REG_LIST.include/ include/ virt/ | +27 | 1 reply | |
| 4/5 | KVM: ARM: Use KVM_VCPU_GET_REG_LIST.arch/ arch/ arch/ +2 more | +5 | 1 reply | |
| 5/5 | KVM: ARM: Access all registers via KVM_GET_ONE_REG/KVM_SET_ONE_REG.arch/ arch/ arch/ +1 more | +275 | 11 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/5] Making KVM_GET_ONE_REG/KVM_SET_ONE_REG generic.
Hi all,
This compiles, completely untested, but it's my attempt to give
Avi (and Alexander) what he asked for in a generic register accessor.
Mingled in these patches is the conversion of the latest KVM ARM code, which is the first proposed user: by the end, we use these accessors for *every* register and piece of state.
GET_MULTI/SET_MULTI is an obvious extension which is not yet implemented.
Comments please!
Rusty.