From: Alexandru Elisei <alexandru.elisei@arm.com>
To: linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org
Subject: [PATCH v2 0/2] KVM: arm64: Documentation updates
Date: Thu, 24 Sep 2020 13:37:29 +0100 [thread overview]
Message-ID: <20200924123731.268177-1-alexandru.elisei@arm.com> (raw)
I noticed some discrepancies between the error codes returned by KVM PMU
emulation and the documentation, this is my attempt at fixing them.
The code is from the original implementation of KVM PMU, and I thought it
would be more prudent to modify the documentation to match the code instead
of the other way around.
Changes since v1:
- Added Reviewed-by from Andrew Jones for #1. Thank you!
- Changed -ENXIO description for KVM_ARM_VCPU_PMU_V3_IRQ in #2 to take into
account the case where KVM_GET_DEVICE_ATTR is called and the irq number
is not set.
Alexandru Elisei (2):
KVM: arm64: Add undocumented return values for PMU device control
group
KVM: arm64: Match PMU error code descriptions with error conditions
Documentation/virt/kvm/devices/vcpu.rst | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
--
2.28.0
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2020-09-24 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 12:37 Alexandru Elisei [this message]
2020-09-24 12:37 ` [PATCH v2 1/2] KVM: arm64: Add undocumented return values for PMU device control group Alexandru Elisei
2020-09-24 12:37 ` [PATCH v2 2/2] KVM: arm64: Match PMU error code descriptions with error conditions Alexandru Elisei
2020-09-24 12:59 ` Andrew Jones
2020-09-30 7:31 ` [PATCH v2 0/2] KVM: arm64: Documentation updates Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200924123731.268177-1-alexandru.elisei@arm.com \
--to=alexandru.elisei@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).