Searched hist:b22216e1a617ca55b41337cd1e057ebc784a65d4 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/arch/arm64/kvm/ |
| H A D | hypercalls.c | diff b22216e1a617ca55b41337cd1e057ebc784a65d4 Mon May 02 18:38:48 CDT 2022 Raghavendra Rao Ananta <rananta@google.com> KVM: arm64: Add vendor hypervisor firmware register
Introduce the firmware register to hold the vendor specific
hypervisor service calls (owner value 6) as a bitmap. The
bitmap represents the features that'll be enabled for the
guest, as configured by the user-space. Currently, this
includes support for KVM-vendor features along with
reading the UID, represented by bit-0, and Precision Time
Protocol (PTP), represented by bit-1.
Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
[maz: tidy-up bitmap values]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220502233853.1233742-5-rananta@google.com
|
| /openbmc/linux/arch/arm64/include/uapi/asm/ |
| H A D | kvm.h | diff b22216e1a617ca55b41337cd1e057ebc784a65d4 Mon May 02 18:38:48 CDT 2022 Raghavendra Rao Ananta <rananta@google.com> KVM: arm64: Add vendor hypervisor firmware register
Introduce the firmware register to hold the vendor specific
hypervisor service calls (owner value 6) as a bitmap. The
bitmap represents the features that'll be enabled for the
guest, as configured by the user-space. Currently, this
includes support for KVM-vendor features along with
reading the UID, represented by bit-0, and Precision Time
Protocol (PTP), represented by bit-1.
Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
[maz: tidy-up bitmap values]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220502233853.1233742-5-rananta@google.com
|
| /openbmc/linux/arch/arm64/include/asm/ |
| H A D | kvm_host.h | diff b22216e1a617ca55b41337cd1e057ebc784a65d4 Mon May 02 18:38:48 CDT 2022 Raghavendra Rao Ananta <rananta@google.com> KVM: arm64: Add vendor hypervisor firmware register
Introduce the firmware register to hold the vendor specific
hypervisor service calls (owner value 6) as a bitmap. The
bitmap represents the features that'll be enabled for the
guest, as configured by the user-space. Currently, this
includes support for KVM-vendor features along with
reading the UID, represented by bit-0, and Precision Time
Protocol (PTP), represented by bit-1.
Signed-off-by: Raghavendra Rao Ananta <rananta@google.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
[maz: tidy-up bitmap values]
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220502233853.1233742-5-rananta@google.com
|