Messages in this thread - First message in thread
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
- "Suthikulpanit, Suravee"
| | | Subject | Re: [PATCH v2 04/15] kvm: x86: Add per-VM APICv state debugfs | From | Alexander Graf <> | Date | Mon, 19 Aug 2019 11:57:13 +0200 |
| |
On 15.08.19 18:25, Suthikulpanit, Suravee wrote: > Currently, there is no way to tell whether APICv is active > on a particular VM. This often cause confusion since APICv > can be deactivated at runtime. > > Introduce a debugfs entry to report APICv state of a VM. > This creates a read-only file: > > /sys/kernel/debug/kvm/70860-14/apicv-state > > Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Shouldn't this first and foremost be a VM ioctl so that user space can inquire its own state?
Alex
| |