Bagas Sanjaya bagasdotme@gmail.com 于2023年4月15日周六 11:24写道：
On Fri, Apr 14, 2023 at 07:00:53PM +0800, Jinrong Liang wrote:
+Specifically, KVM follows the following pseudo-code when determining whether to +allow the guest FixCtr[i] to count its pre-defined fixed event:
- FixCtr[i]_is_allowed = (action == ALLOW) && (bitmap & BIT(i)) ||
- (action == DENY) && !(bitmap & BIT(i));
- FixCtr[i]_is_denied = !FixCtr[i]_is_allowed;
As kernel test robot has reported [1], you need to wrap the code above in a code block:
I will make the changes as you suggested, i.e. wrap the code above in a code block.
Thanks.
---- >8 ---- diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index 036f5b1a39aff8..b5836767e0e76d 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -5126,7 +5126,7 @@ Via this API, KVM userspace can also control the behavior of the VM's fixed counters (if any) by configuring the "action" and "fixed_counter_bitmap" fields.
Specifically, KVM follows the following pseudo-code when determining whether to -allow the guest FixCtr[i] to count its pre-defined fixed event: +allow the guest FixCtr[i] to count its pre-defined fixed event::
FixCtr[i]_is_allowed = (action == ALLOW) && (bitmap & BIT(i)) || (action == DENY) && !(bitmap & BIT(i));
Thanks.
-- An old man doll... just what I always wanted! - Clara