From: vijay.kilari@gmail.com (vijay.kilari at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 8/8] arm/arm64: Documentation: Update arm-vgic-v3.txt
Date: Thu, 26 Jan 2017 19:50:53 +0530 [thread overview]
Message-ID: <1485440453-10597-9-git-send-email-vijay.kilari@gmail.com> (raw)
In-Reply-To: <1485440453-10597-1-git-send-email-vijay.kilari@gmail.com>
From: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
Update error code returned for Invalid CPU interface register
value and access in AArch32 mode.
Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
---
Documentation/virtual/kvm/devices/arm-vgic-v3.txt | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/Documentation/virtual/kvm/devices/arm-vgic-v3.txt b/Documentation/virtual/kvm/devices/arm-vgic-v3.txt
index 9348b3c..c1a2461 100644
--- a/Documentation/virtual/kvm/devices/arm-vgic-v3.txt
+++ b/Documentation/virtual/kvm/devices/arm-vgic-v3.txt
@@ -118,7 +118,7 @@ Groups:
-EBUSY: One or more VCPUs are running
- KVM_DEV_ARM_VGIC_CPU_SYSREGS
+ KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS
Attributes:
The attr field of kvm_device_attr encodes two values:
bits: | 63 .... 32 | 31 .... 16 | 15 .... 0 |
@@ -139,13 +139,15 @@ Groups:
All system regs accessed through this API are (rw, 64-bit) and
kvm_device_attr.addr points to a __u64 value.
- KVM_DEV_ARM_VGIC_CPU_SYSREGS accesses the CPU interface registers for the
+ KVM_DEV_ARM_VGIC_GRP_CPU_SYSREGS accesses the CPU interface registers for the
CPU specified by the mpidr field.
+ CPU interface registers access is not implemented for AArch32 mode.
+ Error -ENXIO is returned when accessed in AArch32 mode.
Errors:
-ENXIO: Getting or setting this register is not yet supported
-EBUSY: VCPU is running
- -EINVAL: Invalid mpidr supplied
+ -EINVAL: Invalid mpidr or register value supplied
KVM_DEV_ARM_VGIC_GRP_NR_IRQS
@@ -204,3 +206,6 @@ Groups:
architecture defined MPIDR, and the field is encoded as follows:
| 63 .... 56 | 55 .... 48 | 47 .... 40 | 39 .... 32 |
| Aff3 | Aff2 | Aff1 | Aff0 |
+ Errors:
+ -EINVAL: vINTID is not multiple of 32 or
+ info field is not VGIC_LEVEL_INFO_LINE_LEVEL
--
1.9.1
next prev parent reply other threads:[~2017-01-26 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 14:20 [PATCH v11 0/8] arm/arm64: vgic: Implement API for vGICv3 live migration vijay.kilari at gmail.com
2017-01-26 14:20 ` [PATCH v11 1/8] arm/arm64: vgic: Implement support for userspace access vijay.kilari at gmail.com
2017-01-26 20:34 ` Christoffer Dall
2017-01-27 8:05 ` Auger Eric
2017-01-26 14:20 ` [PATCH v11 2/8] arm/arm64: vgic: Add distributor and redistributor access vijay.kilari at gmail.com
2017-01-27 8:13 ` Auger Eric
2017-01-26 14:20 ` [PATCH v11 3/8] arm/arm64: vgic: Introduce find_reg_by_id() vijay.kilari at gmail.com
2017-01-26 14:20 ` [PATCH v11 4/8] irqchip/gic-v3: Add missing system register definitions vijay.kilari at gmail.com
2017-01-26 14:20 ` [PATCH v11 5/8] arm/arm64: vgic: Introduce VENG0 and VENG1 fields to vmcr struct vijay.kilari at gmail.com
2017-01-27 8:18 ` Auger Eric
2017-01-26 14:20 ` [PATCH v11 6/8] arm/arm64: vgic: Implement VGICv3 CPU interface access vijay.kilari at gmail.com
2017-01-26 20:24 ` Christoffer Dall
2017-01-27 8:21 ` Auger Eric
2017-01-26 14:20 ` [PATCH v11 7/8] arm/arm64: vgic: Implement KVM_DEV_ARM_VGIC_GRP_LEVEL_INFO ioctl vijay.kilari at gmail.com
2017-01-26 18:02 ` Christoffer Dall
2017-01-27 8:32 ` Auger Eric
2017-01-27 8:37 ` Auger Eric
2017-01-26 14:20 ` vijay.kilari at gmail.com [this message]
2017-01-26 20:24 ` [PATCH v11 8/8] arm/arm64: Documentation: Update arm-vgic-v3.txt Christoffer Dall
2017-01-27 8:39 ` Auger Eric
2017-01-26 20:26 ` [PATCH v11 0/8] arm/arm64: vgic: Implement API for vGICv3 live migration Christoffer Dall
2017-01-27 9:45 ` Marc Zyngier
2017-01-27 10:27 ` Christoffer Dall
2017-01-27 9:03 ` Auger Eric
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=1485440453-10597-9-git-send-email-vijay.kilari@gmail.com \
--to=vijay.kilari@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).