diff options
| author | Igor Mammedov <imammedo@redhat.com> | 2019-12-09 14:09:00 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2020-01-22 00:23:07 -0500 |
| commit | e6d0c3ce689585ad8f38c826e69ee04fb2c2257c (patch) | |
| tree | ab0a6898772ef9ee98e1a06a4cd8b1ed091b4943 /docs/specs | |
| parent | 5b8e5363faa19f6f5064df7f3830c7b56d80f28d (diff) | |
| download | qemu-e6d0c3ce689585ad8f38c826e69ee04fb2c2257c.zip qemu-e6d0c3ce689585ad8f38c826e69ee04fb2c2257c.tar.gz qemu-e6d0c3ce689585ad8f38c826e69ee04fb2c2257c.tar.bz2 | |
acpi: cpuhp: introduce 'Command data 2' field
No functional change in practice, patch only aims to properly
document (in spec and code) intended usage of the reserved space.
The new field is to be used for 2 purposes:
- detection of modern CPU hotplug interface using
CPHP_GET_NEXT_CPU_WITH_EVENT_CMD command.
procedure will be described in follow up patch:
"acpi: cpuhp: spec: add typical usecases"
- for returning upper 32 bits of architecture specific CPU ID,
for new CPHP_GET_CPU_ID_CMD command added by follow up patch:
"acpi: cpuhp: add CPHP_GET_CPU_ID_CMD command"
Change is backward compatible with 4.2 and older machines, as field was
unconditionally reserved and always returned 0x0 if modern CPU hotplug
interface was enabled.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <1575896942-331151-8-git-send-email-imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'docs/specs')
| -rw-r--r-- | docs/specs/acpi_cpu_hotplug.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/specs/acpi_cpu_hotplug.txt b/docs/specs/acpi_cpu_hotplug.txt index 8fb9ad2..9879f9e 100644 --- a/docs/specs/acpi_cpu_hotplug.txt +++ b/docs/specs/acpi_cpu_hotplug.txt @@ -44,7 +44,10 @@ keeps the current value. read access: offset: - [0x0-0x3] reserved + [0x0-0x3] Command data 2: (DWORD access) + if value last stored in 'Command field': + 0: reads as 0x0 + other values: reserved [0x4] CPU device status fields: (1 byte access) bits: 0: Device is enabled and may be used by guest |