Sorry for the delay, it looks like this patch resolves the issue.
Tested-by: Crawford, Eric R
-Eric
-Original Message-
From: Gao, Chao
Sent: Monday, August 28, 2017 12:27 AM
To: Crawford, Eric R
Cc: Andrew Cooper
On Mon, Aug 28, 2017 at 02:16:18AM -0600, Jan Beulich wrote:
On 28.08.17 at 04:42, wrote:
>> When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function'
>> are under the scope of the same VT-d unit as the 'Physical Function'.
>> A 'Physical Function' can be a
>>> On 28.08.17 at 04:42, wrote:
> When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function'
> are under the scope of the same VT-d unit as the 'Physical Function'.
> A 'Physical Function' can be a 'Traditional Function' or an ARI
> 'Extended Function'. And
> From: Gao, Chao
> Sent: Monday, August 28, 2017 10:42 AM
>
> When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function'
> are under the scope of the same VT-d unit as the 'Physical Function'.
> A 'Physical Function' can be a 'Traditional Function' or an ARI
> 'Extended Function'. And
When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function'
are under the scope of the same VT-d unit as the 'Physical Function'.
A 'Physical Function' can be a 'Traditional Function' or an ARI
'Extended Function'. And furthermore, 'Extended Functions' on an
endpoint are under the scope