diff mbox series

[net-next,5/5] ibmvnic: Provide documentation for ACL sysfs files

Message ID 1598893093-14280-6-git-send-email-tlfalcon@linux.ibm.com
State New
Headers show
Series [net-next,1/5] ibmvnic: Create failover sysfs as part of an attribute group | expand

Commit Message

Thomas Falcon Aug. 31, 2020, 4:58 p.m. UTC
Provide documentation for ibmvnic device Access Control List
files.

Signed-off-by: Thomas Falcon <tlfalcon@linux.ibm.com>
---
 Documentation/ABI/testing/sysfs-driver-ibmvnic | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

Comments

Thomas Falcon Aug. 31, 2020, 7:54 p.m. UTC | #1
On 8/31/20 2:26 PM, Jakub Kicinski wrote:
> On Mon, 31 Aug 2020 11:58:13 -0500 Thomas Falcon wrote:
>> Provide documentation for ibmvnic device Access Control List
>> files.
> What API is used to set those parameters in the first place?
>
These parameters are specified in the system's IBM Hardware Management 
Console (HMC) when the VNIC device is create.
Jakub Kicinski Aug. 31, 2020, 8:11 p.m. UTC | #2
On Mon, 31 Aug 2020 14:54:06 -0500 Thomas Falcon wrote:
> On 8/31/20 2:26 PM, Jakub Kicinski wrote:
> > On Mon, 31 Aug 2020 11:58:13 -0500 Thomas Falcon wrote:  
> >> Provide documentation for ibmvnic device Access Control List
> >> files.  
> > What API is used to set those parameters in the first place?
> >  
> These parameters are specified in the system's IBM Hardware Management 
> Console (HMC) when the VNIC device is create.

The new attributes are visible in the "guest" OS, correct?

This seems similar to normal SR-IOV operation, but I've not heard of
use cases for them VM to know what its pvid is. Could you elaborate?
Thomas Falcon Aug. 31, 2020, 9:44 p.m. UTC | #3
On 8/31/20 3:11 PM, Jakub Kicinski wrote:
> On Mon, 31 Aug 2020 14:54:06 -0500 Thomas Falcon wrote:
>> On 8/31/20 2:26 PM, Jakub Kicinski wrote:
>>> On Mon, 31 Aug 2020 11:58:13 -0500 Thomas Falcon wrote:
>>>> Provide documentation for ibmvnic device Access Control List
>>>> files.
>>> What API is used to set those parameters in the first place?
>>>   
>> These parameters are specified in the system's IBM Hardware Management
>> Console (HMC) when the VNIC device is create.
> The new attributes are visible in the "guest" OS, correct?

Correct.

>
> This seems similar to normal SR-IOV operation, but I've not heard of
> use cases for them VM to know what its pvid is. Could you elaborate?
It's provided for informational purposes.
diff mbox series

Patch

diff --git a/Documentation/ABI/testing/sysfs-driver-ibmvnic b/Documentation/ABI/testing/sysfs-driver-ibmvnic
index 7fa2920..8c78312 100644
--- a/Documentation/ABI/testing/sysfs-driver-ibmvnic
+++ b/Documentation/ABI/testing/sysfs-driver-ibmvnic
@@ -12,3 +12,29 @@  Description:	If the ibmvnic device has been configured with redundant
 		returned.
 Users:		Any users of the ibmvnic driver which use redundant hardware
 		configurations.
+
+What:		/sys/devices/vio/<our device>/mac_acls
+Date:		August 2020
+KernelVersion:	5.10
+Contact:	linuxppc-dev@lists.ozlabs.org
+Description:	Read-only file which lists the current entries in the ibmvnic
+		device's MAC address Access Control List. Each entry is
+		separated by a new line.
+Users:		Any users of the ibmvnic driver
+
+What:		/sys/devices/vio/<our device>/vlan_acls
+Date:		August 2020
+KernelVersion:	5.10
+Contact:	linuxppc-dev@lists.ozlabs.org
+Description:	Read-only file which lists the current entries in the ibmvnic
+		device's VLAN ID Access Control List. Each entry is separated
+		by a new line.
+Users:		Any users of the ibmvnic driver
+
+What:		/sys/devices/vio/<our device>/pvid
+Date:		August 2020
+KernelVersion:	5.10
+Contact:	linuxppc-dev@lists.ozlabs.org
+Description:	Read-only file which lists the ibmvnic device's Port VLAN
+		ID and Priority setting. Each entry is separated by a new line.
+Users:		Any users of the ibmvnic driver