> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, August 25, 2017 11:20 PM
>
>
> > Currently, VF won't implement SRIOV feature, seeing
> > SRIOV specv1.1 chapter 3.7 PCI Express Extended Capabilities. Even VF
> > will implement SRIOV later, I think as long as a function is SRIOV
> >
On Fri, Aug 25, 2017 at 09:20:23AM -0600, Jan Beulich wrote:
On 25.08.17 at 15:51, wrote:
>> On Fri, Aug 25, 2017 at 03:39:38AM -0600, Jan Beulich wrote:
>> On 25.08.17 at 07:27, wrote:
When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function' are
under
the sco
>>> On 25.08.17 at 15:51, wrote:
> On Fri, Aug 25, 2017 at 03:39:38AM -0600, Jan Beulich wrote:
> On 25.08.17 at 07:27, 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
>>
On Fri, Aug 25, 2017 at 03:39:38AM -0600, Jan Beulich wrote:
On 25.08.17 at 07:27, 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 Functio
>>> On 25.08.17 at 07:27, 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 furthermore, 'Extended Functi
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 of
