On 6/18/19 2:49 AM, Harald Freudenberger wrote:
On 17.06.19 17:07, Tony Krowiak wrote:
On 6/17/19 6:05 AM, Harald Freudenberger wrote:
On 13.06.19 21:39, Tony Krowiak wrote:
The AP architecture does not preclude assignment of AP resources that are
not available. Let's go ahead and implement th
On 17.06.19 17:07, Tony Krowiak wrote:
> On 6/17/19 6:05 AM, Harald Freudenberger wrote:
>> On 13.06.19 21:39, Tony Krowiak wrote:
>>> The AP architecture does not preclude assignment of AP resources that are
>>> not available. Let's go ahead and implement this facet of the AP
>>> architecture for
On 6/17/19 6:05 AM, Harald Freudenberger wrote:
On 13.06.19 21:39, Tony Krowiak wrote:
The AP architecture does not preclude assignment of AP resources that are
not available. Let's go ahead and implement this facet of the AP
architecture for linux guests.
The current implementation does not al
On 13.06.19 21:39, Tony Krowiak wrote:
> The AP architecture does not preclude assignment of AP resources that are
> not available. Let's go ahead and implement this facet of the AP
> architecture for linux guests.
>
> The current implementation does not allow assignment of AP adapters or
> domains
The AP architecture does not preclude assignment of AP resources that are
not available. Let's go ahead and implement this facet of the AP
architecture for linux guests.
The current implementation does not allow assignment of AP adapters or
domains to an mdev device if the APQNs resulting from the
5 matches
Mail list logo
