Re: [libvirt] [PATCH 0/3 RFC] macvtap: Implement getPhysfn to support sending a port profile message for a VF to its PF

2011-08-02 Thread Roopa Prabhu
On 8/2/11 4:15 AM, "Daniel P. Berrange" wrote: > On Mon, Aug 01, 2011 at 09:16:09PM -0400, Dave Allan wrote: >> On Mon, Aug 01, 2011 at 04:56:58PM -0700, Roopa Prabhu wrote: >>> This patch tries to fix getPhysFn in macvtap.c to get the physical >>> function(PF) of the direct attach interface,

Re: [libvirt] [PATCH 0/3 RFC] macvtap: Implement getPhysfn to support sending a port profile message for a VF to its PF

2011-08-02 Thread Daniel P. Berrange
On Mon, Aug 01, 2011 at 09:16:09PM -0400, Dave Allan wrote: > On Mon, Aug 01, 2011 at 04:56:58PM -0700, Roopa Prabhu wrote: > > This patch tries to fix getPhysFn in macvtap.c to get the physical > > function(PF) of the direct attach interface, if the interface is a SR-IOV > > VF. > > It derives t

Re: [libvirt] [PATCH 0/3 RFC] macvtap: Implement getPhysfn to support sending a port profile message for a VF to its PF

2011-08-01 Thread Dave Allan
On Mon, Aug 01, 2011 at 04:56:58PM -0700, Roopa Prabhu wrote: > This patch tries to fix getPhysFn in macvtap.c to get the physical > function(PF) of the direct attach interface, if the interface is a SR-IOV VF. > It derives the PF/VF relationship from sysfs. > > There is some code to do this in n

[libvirt] [PATCH 0/3 RFC] macvtap: Implement getPhysfn to support sending a port profile message for a VF to its PF

2011-08-01 Thread Roopa Prabhu
This patch tries to fix getPhysFn in macvtap.c to get the physical function(PF) of the direct attach interface, if the interface is a SR-IOV VF. It derives the PF/VF relationship from sysfs. There is some code to do this in node device driver. But it is local to the node device driver . I did not