xen/pv: sanitize xen pv guest msr accesses
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest4 patches 2 repliesIn review
- v23 patches 6 repliesSuperseded
- v13 patches 6 repliesSuperseded
Changes in v3 from the cover letter
- new patch 2
- addressed comments
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | xen/pv: add fault recovery control to pmu msr accessesarch/ | +38 | 1 reply | |
| 2/4 | xen/pv: fix vendor checks for pmu emulationarch/ | +6 | 1 reply | |
| 3/4 | xen/pv: refactor msr access functions to support safe and unsafe accessesarch/ | +56 | 0 replies | |
| 4/4 | xen/pv: support selecting safe/unsafe msr accessesDocumentation/ arch/ arch/ | +29 | 0 replies |
Reviews trailers per patch
3 of 4 patches have a Reviewed-by or Acked-by.
| Patch | Jan Beulich |
|---|---|
| 1/4 | R-b |
| 2/4 | R-b |
| 3/4 | R-b |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/4] xen/pv: sanitize xen pv guest msr accesses
Historically when running as Xen PV guest all MSR accesses have been silently swallowing any GP faults, even when the kernel was using not the *msr_safe() access functions.
Change that by making the behavior controllable via kernel config and via a boot parameter.
This will help finding paths where MSRs are being accessed under Xen which are not emulated by the hypervisor.
Changes in V3:
- new patch 2
- addressed comments
Juergen Gross (4):
xen/pv: add fault recovery control to pmu msr accesses xen/pv: fix vendor checks for pmu emulation
xen/pv: refactor msr access functions to support safe and unsafe
accesses
xen/pv: support selecting safe/unsafe msr accesses
.../admin-guide/kernel-parameters.txt | 6 ++ arch/x86/xen/Kconfig | 9 ++ arch/x86/xen/enlighten_pv.c | 99 +++++++++++++------ arch/x86/xen/pmu.c | 71 +++++++------ 4 files changed, 127 insertions(+), 58 deletions(-)
Signature · 1 line
2.35.3