On Thu, Jan 09, 2020 at 11:25:04AM +0000, Andrew Murray wrote:

On Thu, Jan 09, 2020 at 11:23:37AM +0000, Andrew Murray wrote:

quoted

On Wed, Jan 08, 2020 at 01:10:21PM +0000, Will Deacon wrote:

quoted

On Wed, Jan 08, 2020 at 12:36:11PM +0000, Marc Zyngier wrote:

quoted

On 2020-01-08 11:58, Will Deacon wrote:

quoted

On Wed, Jan 08, 2020 at 11:17:16AM +0000, Marc Zyngier wrote:

quoted

On 2020-01-07 15:13, Andrew Murray wrote:

quoted

Looking at the vcpu_load and related code, I don't see a way of saying
'don't schedule this VCPU on this CPU' or bailing in any way.

That would actually be pretty easy to implement. In vcpu_load(), check
that that the CPU physical has SPE. If not, raise a request for that
vcpu.
In the run loop, check for that request and abort if raised, returning
to userspace.

I hadn't really noticed the kvm_make_request mechanism - however it's now
clear how this could be implemented.

This approach gives responsibility for which CPUs should be used to userspace
and if userspace gets it wrong then the KVM_RUN ioctl won't do very much.

quoted

quoted

quoted

quoted

Userspace can always check /sys/devices/arm_spe_0/cpumask and work out
where to run that particular vcpu.

It's also worth considering systems where there are multiple
implementations
of SPE in play. Assuming we don't want to expose this to a guest, then
the
right interface here is probably for userspace to pick one SPE
implementation and expose that to the guest.

If I understand correctly then this implies the following:

 - If the host userspace indicates it wants support for SPE in the guest (via 
   KVM_SET_DEVICE_ATTR at start of day) - then we should check in vcpu_load that
   the minimum version of SPE is present on the current CPU. 'minimum' because
   we don't know why userspace has selected the given cpumask.

 - Userspace can get it wrong, i.e. it can create a CPU mask with CPUs that
   have SPE with differing versions. If it does, and all CPUs have some form of
   SPE then errors may occur in the guest. Perhaps this is OK and userspace
   shouldn't get it wrong?

Actually this could be guarded against by emulating the ID_AA64DFR0_EL1 such to
cap the version to the minimum SPE version - if absolutely required.

The problem is, it's not as simple as checking a version field. Instead,
you'd have to look at all of the ID registers for SPE so that you don't end
up with funny differences such as minimum sampling interval, or hardware RNG
support. Ultimately though, *much* of the trace is going to be describing
IMP DEF stuff because it's so micro-architectural, and there's very little
you can do to hide that.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel