From: Christoffer Dall <christoffer.dall@arm.com> To: Marc Zyngier <marc.zyngier@arm.com> Cc: kvm@vger.kernel.org, Andre Przywara <andre.przywara@arm.com>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 9/9] KVM: arm/arm64: vgic: Update documentation of the GICv2 device Date: Mon, 16 Jul 2018 11:54:44 +0200 [thread overview] Message-ID: <20180716095444.GB30822@e113682-lin.lund.arm.com> (raw) In-Reply-To: <a5324e35-53b4-b5b4-84a2-1e0a89b244e7@arm.com> On Mon, Jul 16, 2018 at 09:52:04AM +0100, Marc Zyngier wrote: > On 14/07/18 18:05, Christoffer Dall wrote: > > Update the documentation to reflect the ordering requirements of > > restoring GICv2 distributor registers and remove outdated limitations in > > the documentation while we're at it. > > > > Signed-off-by: Christoffer Dall <christoffer.dall@arm.com> > > --- > > Documentation/virtual/kvm/devices/arm-vgic.txt | 12 ++++++------ > > 1 file changed, 6 insertions(+), 6 deletions(-) > > > > diff --git a/Documentation/virtual/kvm/devices/arm-vgic.txt b/Documentation/virtual/kvm/devices/arm-vgic.txt > > index b3ce126..c9a6393 100644 > > --- a/Documentation/virtual/kvm/devices/arm-vgic.txt > > +++ b/Documentation/virtual/kvm/devices/arm-vgic.txt > > @@ -49,9 +49,12 @@ Groups: > > index is specified with the vcpu_index field. Note that most distributor > > fields are not banked, but return the same value regardless of the > > vcpu_index used to access the register. > > - Limitations: > > - - Priorities are not implemented, and registers are RAZ/WI > > - - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2. > > + > > + GICD_IIDR.Revision is updated when the KVM implementation of an emulated > > + GICv2 is changed. Userspace should read GICD_IIDR from KVM and write back > > + the read value to confirm its expected behavior is aligned with the KVM > > + implementation. To properly restore the interrupt group configuration, > > + GICD_IIDR should be written before any other registers. > > I'd like to make it crystal clear that writing to IIDR doesn't allow to > select a behaviour, and is merely a confirmation that host and guest do > agree on either revision 0 (no write) or revision n (n being read and > written back). > > Also, on ordering: does the write to IIDR have to happen before any > write to other distributor registers? Or to any GIC register? I think > you mean the former, but I wonder if we shouldn't mandate the latter, > just to be sure... > I was thinking that IIDR should simply be the very first thing you write, I'll clarify the intent. > > Errors: > > -ENXIO: Getting or setting this register is not yet supported > > -EBUSY: One or more VCPUs are running > > @@ -94,9 +97,6 @@ Groups: > > use the lower 5 bits to communicate with the KVM device and must shift the > > value left by 3 places to obtain the actual priority mask level. > > > > - Limitations: > > - - Priorities are not implemented, and registers are RAZ/WI > > - - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2. > > Errors: > > -ENXIO: Getting or setting this register is not yet supported > > -EBUSY: One or more VCPUs are running > > > > Finally, do we want to to extend the same requirements to GICv3, for the > sake of uniformity? Probably. I'll check the userspace implementation if that would break compatibility with today. Thanks, -Christoffer IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@arm.com (Christoffer Dall) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 9/9] KVM: arm/arm64: vgic: Update documentation of the GICv2 device Date: Mon, 16 Jul 2018 11:54:44 +0200 [thread overview] Message-ID: <20180716095444.GB30822@e113682-lin.lund.arm.com> (raw) In-Reply-To: <a5324e35-53b4-b5b4-84a2-1e0a89b244e7@arm.com> On Mon, Jul 16, 2018 at 09:52:04AM +0100, Marc Zyngier wrote: > On 14/07/18 18:05, Christoffer Dall wrote: > > Update the documentation to reflect the ordering requirements of > > restoring GICv2 distributor registers and remove outdated limitations in > > the documentation while we're at it. > > > > Signed-off-by: Christoffer Dall <christoffer.dall@arm.com> > > --- > > Documentation/virtual/kvm/devices/arm-vgic.txt | 12 ++++++------ > > 1 file changed, 6 insertions(+), 6 deletions(-) > > > > diff --git a/Documentation/virtual/kvm/devices/arm-vgic.txt b/Documentation/virtual/kvm/devices/arm-vgic.txt > > index b3ce126..c9a6393 100644 > > --- a/Documentation/virtual/kvm/devices/arm-vgic.txt > > +++ b/Documentation/virtual/kvm/devices/arm-vgic.txt > > @@ -49,9 +49,12 @@ Groups: > > index is specified with the vcpu_index field. Note that most distributor > > fields are not banked, but return the same value regardless of the > > vcpu_index used to access the register. > > - Limitations: > > - - Priorities are not implemented, and registers are RAZ/WI > > - - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2. > > + > > + GICD_IIDR.Revision is updated when the KVM implementation of an emulated > > + GICv2 is changed. Userspace should read GICD_IIDR from KVM and write back > > + the read value to confirm its expected behavior is aligned with the KVM > > + implementation. To properly restore the interrupt group configuration, > > + GICD_IIDR should be written before any other registers. > > I'd like to make it crystal clear that writing to IIDR doesn't allow to > select a behaviour, and is merely a confirmation that host and guest do > agree on either revision 0 (no write) or revision n (n being read and > written back). > > Also, on ordering: does the write to IIDR have to happen before any > write to other distributor registers? Or to any GIC register? I think > you mean the former, but I wonder if we shouldn't mandate the latter, > just to be sure... > I was thinking that IIDR should simply be the very first thing you write, I'll clarify the intent. > > Errors: > > -ENXIO: Getting or setting this register is not yet supported > > -EBUSY: One or more VCPUs are running > > @@ -94,9 +97,6 @@ Groups: > > use the lower 5 bits to communicate with the KVM device and must shift the > > value left by 3 places to obtain the actual priority mask level. > > > > - Limitations: > > - - Priorities are not implemented, and registers are RAZ/WI > > - - Currently only implemented for KVM_DEV_TYPE_ARM_VGIC_V2. > > Errors: > > -ENXIO: Getting or setting this register is not yet supported > > -EBUSY: One or more VCPUs are running > > > > Finally, do we want to to extend the same requirements to GICv3, for the > sake of uniformity? Probably. I'll check the userspace implementation if that would break compatibility with today. Thanks, -Christoffer IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2018-07-16 9:54 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-14 17:05 [PATCH v3 0/9] KVM: arm/arm64: vgic: Virtual interrupt grouping support Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 1/9] KVM: arm/arm64: vgic: Define GICD_IIDR fields for GICv2 and GIv3 Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 2/9] KVM: arm/arm64: vgic: Keep track of implementation revision Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 3/9] KVM: arm/arm64: vgic: GICv2 IGROUPR should read as zero Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 4/9] KVM: arm/arm64: vgic: Add group field to struct irq Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 5/9] KVM: arm/arm64: vgic: Signal IRQs using their configured group Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 6/9] KVM: arm/arm64: vgic: Allow configuration of interrupt groups Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 7/9] KVM: arm/arm64: vgic: Permit uaccess writes to return errors Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-16 8:28 ` Marc Zyngier 2018-07-16 8:28 ` Marc Zyngier 2018-07-16 9:59 ` Christoffer Dall 2018-07-16 9:59 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 8/9] KVM: arm/arm64: vgic: Let userspace opt-in to writable v2 IGROUPR Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-16 8:38 ` Marc Zyngier 2018-07-16 8:38 ` Marc Zyngier 2018-07-16 9:46 ` Christoffer Dall 2018-07-16 9:46 ` Christoffer Dall 2018-07-16 11:39 ` Christoffer Dall 2018-07-16 11:39 ` Christoffer Dall 2018-07-14 17:05 ` [PATCH v3 9/9] KVM: arm/arm64: vgic: Update documentation of the GICv2 device Christoffer Dall 2018-07-14 17:05 ` Christoffer Dall 2018-07-16 8:52 ` Marc Zyngier 2018-07-16 8:52 ` Marc Zyngier 2018-07-16 9:54 ` Christoffer Dall [this message] 2018-07-16 9:54 ` Christoffer Dall 2018-07-16 10:34 ` Christoffer Dall 2018-07-16 10:34 ` Christoffer Dall 2018-07-16 11:07 ` Marc Zyngier 2018-07-16 11:07 ` Marc Zyngier 2018-07-16 11:38 ` Christoffer Dall 2018-07-16 11:38 ` 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=20180716095444.GB30822@e113682-lin.lund.arm.com \ --to=christoffer.dall@arm.com \ --cc=andre.przywara@arm.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=marc.zyngier@arm.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.