From: eric.auger@redhat.com (Auger Eric)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] KVM: arm/arm64: Rename vgic_attr_regs_access to vgic_attr_regs_access_v2
Date: Wed, 17 Aug 2016 07:46:37 +0200 [thread overview]
Message-ID: <ca5b4328-5d9e-d3b7-a922-0d3409a7f3e7@redhat.com> (raw)
In-Reply-To: <20160816173501.21521-3-christoffer.dall@linaro.org>
Hi,
On 16/08/2016 19:35, Christoffer Dall wrote:
> Just a rename so we can implement a v3-specific function later.
>
> We take the chance to get rid of the V2/V3 ops comments as well.
>
> No functional change.
>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
> virt/kvm/arm/vgic/vgic-kvm-device.c | 26 +++++++++++---------------
> 1 file changed, 11 insertions(+), 15 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic/vgic-kvm-device.c b/virt/kvm/arm/vgic/vgic-kvm-device.c
> index 19fa331..163b057 100644
> --- a/virt/kvm/arm/vgic/vgic-kvm-device.c
> +++ b/virt/kvm/arm/vgic/vgic-kvm-device.c
> @@ -294,17 +294,17 @@ static bool lock_all_vcpus(struct kvm *kvm)
> return true;
> }
>
> -/** vgic_attr_regs_access: allows user space to read/write VGIC registers
> - *
> - * @dev: kvm device handle
> - * @attr: kvm device attribute
> - * @reg: address the value is read or written
> - * @is_write: write flag
> +/**
> + * vgic_attr_regs_access_v2 - allows user space to access VGIC v2 state
> *
> + * @dev: kvm device handle
> + * @attr: kvm device attribute
> + * @reg: address the value is read or written
> + * @is_write: true if userspace is writing a register
> */
> -static int vgic_attr_regs_access(struct kvm_device *dev,
> - struct kvm_device_attr *attr,
> - u32 *reg, bool is_write)
> +static int vgic_attr_regs_access_v2(struct kvm_device *dev,
> + struct kvm_device_attr *attr,
> + u32 *reg, bool is_write)
> {
> struct vgic_reg_attr reg_attr;
> gpa_t addr;
> @@ -347,8 +347,6 @@ out:
> return ret;
> }
>
> -/* V2 ops */
> -
> static int vgic_v2_set_attr(struct kvm_device *dev,
> struct kvm_device_attr *attr)
> {
> @@ -367,7 +365,7 @@ static int vgic_v2_set_attr(struct kvm_device *dev,
> if (get_user(reg, uaddr))
> return -EFAULT;
>
> - return vgic_attr_regs_access(dev, attr, ®, true);
> + return vgic_attr_regs_access_v2(dev, attr, ®, true);
> }
> }
>
> @@ -389,7 +387,7 @@ static int vgic_v2_get_attr(struct kvm_device *dev,
> u32 __user *uaddr = (u32 __user *)(long)attr->addr;
> u32 reg = 0;
>
> - ret = vgic_attr_regs_access(dev, attr, ®, false);
> + ret = vgic_attr_regs_access_v2(dev, attr, ®, false);
> if (ret)
> return ret;
> return put_user(reg, uaddr);
> @@ -433,8 +431,6 @@ struct kvm_device_ops kvm_arm_vgic_v2_ops = {
> .has_attr = vgic_v2_has_attr,
> };
>
> -/* V3 ops */
> -
> #ifdef CONFIG_KVM_ARM_VGIC_V3
>
> static int vgic_v3_set_attr(struct kvm_device *dev,
>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
prev parent reply other threads:[~2016-08-17 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 17:34 [PATCH v2 0/2] Rework vgic_attr_regs_access Christoffer Dall
2016-08-16 17:35 ` [PATCH v2 1/2] KVM: arm/arm64: Factor out vgic_attr_regs_access functionality Christoffer Dall
2016-08-17 5:46 ` Auger Eric
2016-08-16 17:35 ` [PATCH v2 2/2] KVM: arm/arm64: Rename vgic_attr_regs_access to vgic_attr_regs_access_v2 Christoffer Dall
2016-08-17 5:46 ` Auger Eric [this message]
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=ca5b4328-5d9e-d3b7-a922-0d3409a7f3e7@redhat.com \
--to=eric.auger@redhat.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).