On Mon, May 13, 2019 at 02:45:12PM +0100, Andrew Jones wrote:
> On Mon, May 13, 2019 at 02:12:48PM +0100, Dave Martin wrote:
> > On Mon, May 13, 2019 at 01:57:40PM +0100, Andrew Jones wrote:
> > > On Mon, May 13, 2019 at 01:41:26PM +0100, Dave Martin wrote:
> > > > On Mon, May 13, 2019 at 01:30:23PM +0100, Andrew Jones wrote:
> > > > > On Mon, May 13, 2019 at 12:26:36PM +0100, Dave Martin wrote:
> > > > > > On Sun, May 12, 2019 at 09:36:22AM +0100, Andrew Jones wrote:
> > > > > > > Introduce another cpu property to control SVE vector lengths,
> > > > > > > sve-vls-map, which allows the user to explicitly select the
> > > > > > > set of vector lengths the guest can use. The map must conform
> > > > > > > to QEMU's limits and architectural constraints, checked when
> > > > > > > the property is set. Inconsistencies with sve-max-vq are also
> > > > > > > checked. The bit number of a set bit in the map represents the
> > > > > > > allowed vector length in number of quadwords.
> > > > > > >
> > > > > > > Note, as the map is implemented with a single 64-bit word we
> > > > > > > currently only support up to 8192-bit vectors. As QEMU and
> > > > > > > KVM only support up to 2048-bit vectors then this sufficient
> > > > > > > now, and probably for some time. Extending the bitmap beyond
> > > > > > > a single word will likely require changing the property to
> > > > > > > a string and adding yet another parser to QEMU.
> > > > > > >
> > > > > > > Signed-off-by: Andrew Jones <drjo...@redhat.com>
> > > > > > > ---
> > > > > > > target/arm/cpu.c | 4 +++
> > > > > > > target/arm/cpu.h | 3 ++
> > > > > > > target/arm/cpu64.c | 70
> > > > > > > +++++++++++++++++++++++++++++++++++++++++---
> > > > > > > target/arm/helper.c | 10 ++++++-
> > > > > > > target/arm/monitor.c | 9 ++++--
> > > > > > > 5 files changed, 88 insertions(+), 8 deletions(-)
> > > > > > >
> > > > > >
> > > > > > [...]
> > > > > >
> > > > > > > diff --git a/target/arm/cpu.h b/target/arm/cpu.h
> > > > > > > index 8292d547e8f9..f0d0ce759ba8 100644
> > > > > > > --- a/target/arm/cpu.h
> > > > > > > +++ b/target/arm/cpu.h
> > > > > > > @@ -920,6 +920,9 @@ struct ARMCPU {
> > > > > > >
> > > > > > > /* Used to set the maximum vector length the cpu will
> > > > > > > support. */
> > > > > > > uint32_t sve_max_vq;
> > > > > > > +
> > > > > > > + /* Each bit represents a supported vector length of (bitnum
> > > > > > > * 16) bytes */
> > > > > > > + uint64_t sve_vls_map;
> > > > > >
> > > > > > Just to be clear, the representation here is different from the
> > > > > > representation in KVM_REG_ARM64_SVE_VLS?
> > > > > >
> > > > > > In the latter, bit n represents vector length ((n + 1) * 16) bytes.
> > > > >
> > > > > KVM also uses bitnum * 16. bitnum is the the bit number, not the
> > > > > shift.
> > > >
> > > > Can you point to the relevant kernel code? This isn't what I thought I
> > > > wrote...
> > >
> > > The Documentation/virtual/kvm/api.txt documentation has
> > >
> > > > if (vq >= SVE_VQ_MIN && vq <= SVE_VQ_MAX &&
> > > > ((vector_lengths[(vq - KVM_ARM64_SVE_VQ_MIN) / 64] >>
> > > > ((vq - KVM_ARM64_SVE_VQ_MIN) % 64)) & 1))
> > > > /* Vector length vq * 16 bytes supported */
> > > > else
> > > > /* Vector length vq * 16 bytes not supported */
> > >
> > > Taking vq=1, we check (vector_lengths[0] >> 0) to see if we have the
> > > length (1 * 16) bytes. Since bitnum 1 is (1 << 0) that means the shift
> > > is zero and (bitnum * 16) is the same as (vq * 16). With ((n + 1) * 16),
> > > n would have to be zero, which is not a valid bitnum, but is a valid
> > > bit shift.
> >
> > OK, so it sounds like the interpretation of the KVM ABI is what I intended.
> >
> > What is "bitnum" though? Most of the time, people seem to number bits
> > starting from 0 -- though of course that's just a convention.
>
> Eh, I see the problem. I used the word 'number', when I meant 'position'.
> Indeed the bit number of bit position 1 is zero. Sorry about the confusion.
> For v2 I can try to ensure I don't use the wrong terminology.
I'm not sure there's an actual problem here. I found the terminology
unfamiliar, that's all.
My main concern was that people might be confused about the kernel ABI
here, but it sounds like your interpretation is as I intended.
But by all means clarify the comments if you think there's a risk of
QEMU folks being confused.
[...]
Cheers
---Dave
