linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/7] arm/arm64: vgic: Implement support for userspace access
Date: Thu, 17 Nov 2016 12:40:16 +0100	[thread overview]
Message-ID: <20161117114016.GA22231@cbox> (raw)
In-Reply-To: <CALicx6vbFj3aoSiqc4n_92rZgONeQVhp-GtTkEhW3=pt9P1hGQ@mail.gmail.com>

On Thu, Nov 17, 2016 at 04:56:53PM +0530, Vijay Kilari wrote:
> On Thu, Nov 17, 2016 at 12:22 AM, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > On Fri, Nov 04, 2016 at 04:43:27PM +0530, vijay.kilari at gmail.com wrote:
> >> From: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
> >>
> >> Read and write of some registers like ISPENDR and ICPENDR
> >> from userspace requires special handling when compared to
> >> guest access for these registers.
> >>
> >> Refer to Documentation/virtual/kvm/devices/arm-vgic-v3.txt
> >> for handling of ISPENDR, ICPENDR registers handling.
> >>
> >> Add infrastructure to support guest and userspace read
> >> and write for the required registers
> >> Also moved vgic_uaccess from vgic-mmio-v2.c to vgic-mmio.c
> >>
> >> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
> >> ---
> >>  virt/kvm/arm/vgic/vgic-mmio-v2.c | 25 ----------
> >>  virt/kvm/arm/vgic/vgic-mmio-v3.c | 98 ++++++++++++++++++++++++++++++++--------
> >>  virt/kvm/arm/vgic/vgic-mmio.c    | 78 ++++++++++++++++++++++++++++----
> >>  virt/kvm/arm/vgic/vgic-mmio.h    | 19 ++++++++
> >>  4 files changed, 169 insertions(+), 51 deletions(-)
> >>
> >> diff --git a/virt/kvm/arm/vgic/vgic-mmio-v2.c b/virt/kvm/arm/vgic/vgic-mmio-v2.c
> >> index b44b359..0b32f40 100644
> >> --- a/virt/kvm/arm/vgic/vgic-mmio-v2.c
> >> +++ b/virt/kvm/arm/vgic/vgic-mmio-v2.c
> >> @@ -406,31 +406,6 @@ int vgic_v2_has_attr_regs(struct kvm_device *dev, struct kvm_device_attr *attr)
> >>       return -ENXIO;
> >>  }
> >>
> >> -/*
> >> - * When userland tries to access the VGIC register handlers, we need to
> >> - * create a usable struct vgic_io_device to be passed to the handlers and we
> >> - * have to set up a buffer similar to what would have happened if a guest MMIO
> >> - * access occurred, including doing endian conversions on BE systems.
> >> - */
> >> -static int vgic_uaccess(struct kvm_vcpu *vcpu, struct vgic_io_device *dev,
> >> -                     bool is_write, int offset, u32 *val)
> >> -{
> >> -     unsigned int len = 4;
> >> -     u8 buf[4];
> >> -     int ret;
> >> -
> >> -     if (is_write) {
> >> -             vgic_data_host_to_mmio_bus(buf, len, *val);
> >> -             ret = kvm_io_gic_ops.write(vcpu, &dev->dev, offset, len, buf);
> >> -     } else {
> >> -             ret = kvm_io_gic_ops.read(vcpu, &dev->dev, offset, len, buf);
> >> -             if (!ret)
> >> -                     *val = vgic_data_mmio_bus_to_host(buf, len);
> >> -     }
> >> -
> >> -     return ret;
> >> -}
> >> -
> >>  int vgic_v2_cpuif_uaccess(struct kvm_vcpu *vcpu, bool is_write,
> >>                         int offset, u32 *val)
> >>  {
> >> diff --git a/virt/kvm/arm/vgic/vgic-mmio-v3.c b/virt/kvm/arm/vgic/vgic-mmio-v3.c
> >> index 0d3c76a..ce2708d 100644
> >> --- a/virt/kvm/arm/vgic/vgic-mmio-v3.c
> >> +++ b/virt/kvm/arm/vgic/vgic-mmio-v3.c
> >> @@ -209,6 +209,62 @@ static unsigned long vgic_mmio_read_v3_idregs(struct kvm_vcpu *vcpu,
> >>       return 0;
> >>  }
> >>
> >> +static unsigned long vgic_v3_uaccess_read_pending(struct kvm_vcpu *vcpu,
> >> +                                               gpa_t addr, unsigned int len)
> >> +{
> >> +     u32 intid = VGIC_ADDR_TO_INTID(addr, 1);
> >> +     u32 value = 0;
> >> +     int i;
> >> +
> >> +     /*
> >> +      * A level triggerred interrupt pending state is latched in both
> >> +      * "soft_pending" and "line_level" variables. Userspace will save
> >> +      * and restore soft_pending and line_level separately.
> >> +      * Refer to Documentation/virtual/kvm/devices/arm-vgic-v3.txt
> >> +      * handling of ISPENDR and ICPENDR.
> >> +      */
> >> +     for (i = 0; i < len * 8; i++) {
> >> +             struct vgic_irq *irq = vgic_get_irq(vcpu->kvm, vcpu, intid + i);
> >> +
> >> +             if (irq->config == VGIC_CONFIG_LEVEL && irq->soft_pending)
> >> +                     value |= (1U << i);
> >> +             if (irq->config == VGIC_CONFIG_EDGE && irq->pending)
> >> +                     value |= (1U << i);
> >> +
> >> +             vgic_put_irq(vcpu->kvm, irq);
> >> +     }
> >> +
> >> +     return value;
> >> +}
> >> +
> >> +static void vgic_v3_uaccess_write_pending(struct kvm_vcpu *vcpu,
> >> +                                       gpa_t addr, unsigned int len,
> >> +                                       unsigned long val)
> >> +{
> >> +     u32 intid = VGIC_ADDR_TO_INTID(addr, 1);
> >> +     int i;
> >> +
> >> +     for (i = 0; i < len * 8; i++) {
> >> +             struct vgic_irq *irq = vgic_get_irq(vcpu->kvm, vcpu, intid + i);
> >> +
> >> +             spin_lock(&irq->irq_lock);
> >> +             if (test_bit(i, &val)) {
> >> +                     irq->pending = true;
> >> +                     irq->soft_pending = true;
> >
> > In the vgic_mmio_write_spending function we only set the soft_pending
> > state to true if the interrupt is a level-triggered interrupt.
> >
> > Should we check if that's the case here as well before setting the
> > soft_pending state?
> 
> Yes, can be done. But it puts hard requirement that irq config should
> be restored
> before updating pending state.

Ah, I see.

ok, I think you should keep it the way it is then, but please add a
comment to that effect.

> In any case, the soft_pending is used only if interrupt is level-triggered.
> 
Yes, indeed.

Thanks,
-Christoffer

  reply	other threads:[~2016-11-17 11:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:13 [PATCH v8 0/7] arm/arm64: vgic: Implement API for vGICv3 live migration vijay.kilari at gmail.com
2016-11-04 11:13 ` [PATCH v8 1/7] arm/arm64: vgic: Implement support for userspace access vijay.kilari at gmail.com
2016-11-16 18:52   ` Christoffer Dall
2016-11-17 11:26     ` Vijay Kilari
2016-11-17 11:40       ` Christoffer Dall [this message]
2016-11-04 11:13 ` [PATCH v8 2/7] arm/arm64: vgic: Add distributor and redistributor access vijay.kilari at gmail.com
2016-11-16 18:52   ` Christoffer Dall
2016-11-04 11:13 ` [PATCH v8 3/7] arm/arm64: vgic: Introduce find_reg_by_id() vijay.kilari at gmail.com
2016-11-04 11:13 ` [PATCH v8 4/7] irqchip/gic-v3: Add missing system register definitions vijay.kilari at gmail.com
2016-11-04 11:13 ` [PATCH v8 5/7] arm/arm64: vgic: Introduce VENG0 and VENG1 fields to vmcr struct vijay.kilari at gmail.com
2016-11-16 18:52   ` Christoffer Dall
2016-11-17 12:42     ` Vijay Kilari
2016-11-17 16:01       ` Christoffer Dall
2016-11-04 11:13 ` [PATCH v8 6/7] arm/arm64: vgic: Implement VGICv3 CPU interface access vijay.kilari at gmail.com
2016-11-16 18:52   ` Christoffer Dall
2016-11-17 15:55     ` Vijay Kilari
2016-11-17 16:09       ` Christoffer Dall
2016-11-18 16:58         ` Vijay Kilari
2016-11-21 10:19           ` Christoffer Dall
2016-11-21 13:26             ` Vijay Kilari
2016-11-21 13:43               ` Christoffer Dall
2016-11-18 18:48         ` Vijay Kilari
2016-11-20 13:20           ` Christoffer Dall
2016-11-21 13:32             ` Vijay Kilari
2016-11-21 13:41               ` Christoffer Dall
2016-11-04 11:13 ` [PATCH v8 7/7] arm/arm64: vgic: Implement KVM_DEV_ARM_VGIC_GRP_LEVEL_INFO ioctl vijay.kilari at gmail.com
2016-11-16 18:52   ` Christoffer Dall
2016-11-16 11:47 ` [PATCH v8 0/7] arm/arm64: vgic: Implement API for vGICv3 live migration Christoffer Dall
2016-11-16 14:54   ` Vijay Kilari
2016-11-16 15:11     ` Christoffer Dall
2016-11-17 11:41 ` Christoffer Dall

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=20161117114016.GA22231@cbox \
    --to=christoffer.dall@linaro.org \
    --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).