On 01/03/2017 01:19 PM, Stefano Stabellini wrote: > On Tue, 3 Jan 2017, Boris Ostrovsky wrote: >> Signed-off-by: Boris Ostrovsky <[email protected]> >> Reviewed-by: Konrad Rzeszutek Wilk <[email protected]> >> --- >> CC: George Dunlap <[email protected]> >> CC: Konrad Rzeszutek Wilk <[email protected]> >> CC: Stefano Stabellini <[email protected]> >> CC: Tim Deegan <[email protected]> >> --- >> Changes in v6: >> * No GPE0 update is needed anymore. >> >> docs/misc/hvmlite.markdown | 11 +++++++++++ >> 1 file changed, 11 insertions(+) >> >> diff --git a/docs/misc/hvmlite.markdown b/docs/misc/hvmlite.markdown >> index 898b8ee..472edee 100644 >> --- a/docs/misc/hvmlite.markdown >> +++ b/docs/misc/hvmlite.markdown >> @@ -75,3 +75,14 @@ info structure that's passed at boot time (field >> rsdp_paddr). >> >> Description of paravirtualized devices will come from XenStore, just as it's >> done for HVM guests. >> + >> +## VCPU hotplug ## >> + >> +VCPU hotplug (e.g. 'xl vcpu-set <domain> <num_vcpus>') for PVHv2 guests >> +follows ACPI model where change in domain's number of VCPUS (stored in >> +domain.avail_vcpus) results in an SCI being sent to the guest. The guest >> +then executes DSDT's PRSC method, updating MADT enable status for the >> +affected VCPU. >> + >> +Updating VCPU number is achieved by having the toolstack issue a write to >> +ACPI's XEN_ACPI_CPU_MAP. > Looking at [email protected], > this is done via domctl. I think it is worth documenting that.
Will do. -boirs _______________________________________________ Xen-devel mailing list [email protected] https://lists.xen.org/xen-devel
