diff options
| author | Dave Martin <Dave.Martin@arm.com> | 2019-04-12 15:28:05 +0300 |
|---|---|---|
| committer | Marc Zyngier <marc.zyngier@arm.com> | 2019-04-18 19:14:02 +0300 |
| commit | 9df2d660c7f37aed7244ec0b920c0749dbb69167 (patch) | |
| tree | 7636369b59ea8097072a7a34e626bfd3a7dc2edb /fs/file.c | |
| parent | 92e68b2b1ba004be55b2094fb8b5c11d0b24d11d (diff) | |
| download | linux-9df2d660c7f37aed7244ec0b920c0749dbb69167.tar.xz | |
KVM: Clarify capability requirements for KVM_ARM_VCPU_FINALIZE
Userspace is only supposed to use KVM_ARM_VCPU_FINALIZE when there
is some vcpu feature that can actually be finalized.
This means that documenting KVM_ARM_VCPU_FINALIZE as available or
not depending on the capabilities present is not helpful.
This patch amends the documentation to describe availability in
terms of which capability is required for each finalizable feature
instead.
In any case, userspace sees the same error (EINVAL) regardless of
whether the given feature is not present or KVM_ARM_VCPU_FINALIZE
is not implemented at all.
No functional change.
Suggested-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Dave Martin <Dave.Martin@arm.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'fs/file.c')
0 files changed, 0 insertions, 0 deletions