Message ID | 20210819193758.149660-3-drjones@redhat.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | target/arm/cpu: Introduce sve_vq_supported bitmap | expand |
On 8/19/21 9:37 PM, Andrew Jones wrote: > bitmap_clear() only clears the given range. While the given > range should be sufficient in this case we might as well be > 100% sure all bits are zeroed by using bitmap_zero(). > > Signed-off-by: Andrew Jones <drjones@redhat.com> > --- > target/arm/kvm64.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
diff --git a/target/arm/kvm64.c b/target/arm/kvm64.c index 59982d470d37..e790d6c9a573 100644 --- a/target/arm/kvm64.c +++ b/target/arm/kvm64.c @@ -740,7 +740,7 @@ void kvm_arm_sve_get_vls(CPUState *cs, unsigned long *map) uint32_t vq = 0; int i, j; - bitmap_clear(map, 0, ARM_MAX_VQ); + bitmap_zero(map, ARM_MAX_VQ); /* * KVM ensures all host CPUs support the same set of vector lengths.
bitmap_clear() only clears the given range. While the given range should be sufficient in this case we might as well be 100% sure all bits are zeroed by using bitmap_zero(). Signed-off-by: Andrew Jones <drjones@redhat.com> --- target/arm/kvm64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)