[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qemu-s390x] [PATCH v2 5/5] s390x/cpumodel: Set up CPU model for AP

From: Tony Krowiak
Subject: Re: [qemu-s390x] [PATCH v2 5/5] s390x/cpumodel: Set up CPU model for AP device support
Date: Mon, 5 Mar 2018 16:22:13 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0

On 03/01/2018 09:36 AM, David Hildenbrand wrote:
On 01.03.2018 15:12, Pierre Morel wrote:
On 28/02/2018 12:40, Cornelia Huck wrote:
On Wed, 28 Feb 2018 11:26:30 +0100
David Hildenbrand <address@hidden> wrote:

Then I request the following change in KVM:

If KVM_S390_VM_CPU_FEAT_AP is enabled in KVM, ECA.28 is _always_ set
(not just if an AP device is configured). This especially makes things a
lot easier when it comes to handling hotplugged CPUs and avoiding race
conditions when enabling these bits as mentioned in the KVM series.

KVM_S390_VM_CPU_FEAT_AP == AP instructions available for the guest
(don't throw an operation exception).

So this feature then really is guest ABI. The instructions are
available. If there is no device configured, bad luck.
Sounds sensible from my POV.

I have a concern with this proposition and with the original code:
Very good, this is exactly what I talked to Conny about yesterday.

Short version: CPU model is guest ABI, everything else is configuration.

1) ap=on is a guest ABI feature saying to the guest you can use AP
Indeed, that's what belongs into the CPU model.

2) How we provide AP instructions to the guest can be done in three
different ways:
   - SIE Interpretation
AP instructions executed on the guest will be interpreted and passed directly
through to a real AP device installed on the host according to the APQN
specified in the instruction, so the AP instructions must be available on the
   - interception with VFIO
AP instructions executed on the guest will be intercepted, and interpreted by QEMU then forwarded to a real AP device installed on the host according to how the AP devices are configured in userspace - i.e., whether there is remapping,
multiplexing or sharing of adapters/domains etc. This also requires that AP
instructions be available on the host.
   - interception with emulation
AP instructions executed on the guest will be intercepted, interpreted by QEMU and emulated. This will not require AP instructions be available on the host.

In all cases above, the need to set ECA_APIE is dependent upon the device
type configured for the guest.

Due to bad AP design we can't handle this like zPCI - completely in
QEMU. That's what should control it.

3) We implement this with a device in QEMU and a certain level kernel

It seems possible to set or not ECA.28 , based on the type of kernel device:
- SIE interpretation -> MATRIX KVM device -> ECA.28
- Interception with VFIO and virtualization -> no ECA.28
- interception with emulation -> no ECA.28

I understand the concern with the vCPU but I think we can handle it with
an indirect variable

SIE interpretation Device + KVM_S390_VM_CPU_FEAT_AP -> set the variable
Then in vCPU initialization set ECA.28 based on this variable.
That's exactly why we have the cpu feature interface. E.g. CMMA -> if
not enabled, not interpreted by HW (however also not intercepted to user
space - no sense in doing that right now).
There are two factors at play here, the device type (i.e., -device vfio_ap) and
the KVM_S390_VM_CPU_FEAT_AP feature. Setting ECA_APIE makes no sense if the
vfio_ap device is not configured. For the passthrough implementation, this
means that the AP bus will successfully load on the guest, but there will
be no AP devices detected. If the expectation is that ap=on will allow access
to AP devices on the guest, that would be a mistaken assumption.

If down the road a new guest AP device is introduced that allows multiplexing, device remapping etc., then it will be necessary to intercept AP instructions
executed on the guest. In this case, if ap=on results in setting ECA_APIE,
then the instructions will be interpreted and passed through to a device
that does not exist because it won't be defined in the guest's CRYCB.

Based on these two scenarios, I think what we are really saying with ap=on
is that the guest will require use of the AP instructions installed on the
host. Whether those instructions are executed as a result of interpretation
by the hardware or because they are executed by the device driver is a
separate matter. So, I am inclined to agree with Pierre for that reason.
ECA_APIE should be set only if ap=on (i.e., AP instructions are available
on the host) and the user of those instructions (i.e., the driver) indicate
an intent to use them.

I think it let us more doors open, what is your opinion?
In general, for now we don't care. The kernel is the only AP bus provider.
True today, but not necessarily in the future.

If KVM presents AP support -> AP feature can be enabled. And it should
always enable it.
I disagree for the reasons stated above.

Once we have a QEMU AP bus implementation, things get more complicated.
We could provide the AP feature also without KVM (like zPCI).
I am not familiar with zPCI, so I can't comment.

But weather or not to enable the KVM control has to be concluded from
the other configuration. Only user space can now that and has to decide
before enabling AP in KVM.

So I think for now we are fine. Later, this might be tricky to check but
not impossible.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]