[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180820160802.1fe8f704.cohuck@redhat.com>
Date: Mon, 20 Aug 2018 16:08:02 +0200
From: Cornelia Huck <cohuck@...hat.com>
To: Tony Krowiak <akrowiak@...ux.vnet.ibm.com>
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, freude@...ibm.com, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, borntraeger@...ibm.com,
kwankhede@...dia.com, bjsdjshi@...ux.vnet.ibm.com,
pbonzini@...hat.com, alex.williamson@...hat.com,
pmorel@...ux.vnet.ibm.com, alifm@...ux.vnet.ibm.com,
mjrosato@...ux.vnet.ibm.com, jjherne@...ux.vnet.ibm.com,
thuth@...hat.com, pasic@...ux.vnet.ibm.com, berrange@...hat.com,
fiuczy@...ux.vnet.ibm.com, buendgen@...ibm.com,
frankja@...ux.ibm.com, Tony Krowiak <akrowiak@...ux.ibm.com>
Subject: Re: [PATCH v9 13/22] s390: vfio-ap: sysfs interface to view matrix
mdev matrix
On Mon, 13 Aug 2018 17:48:10 -0400
Tony Krowiak <akrowiak@...ux.vnet.ibm.com> wrote:
> From: Tony Krowiak <akrowiak@...ux.ibm.com>
>
> Provides a sysfs interface to view the AP matrix configured for the
> mediated matrix device.
>
> The relevant sysfs structures are:
>
> /sys/devices/vfio_ap/matrix/
> ...... [mdev_supported_types]
> ......... [vfio_ap-passthrough]
> ............ [devices]
> ...............[$uuid]
> .................. matrix
>
> To view the matrix configured for the mediated matrix device,
> print the matrix file:
>
> cat matrix
>
> Below are examples of the output from the above command:
>
> Example 1: Adapters and domains assigned
> Assignments:
> Adapters 5 and 6
> Domains 4 and 71 (0x47)
>
> Output
> 05.0004
> 05.0047
> 06.0004
> 06.0047
>
> Examples 2: Only adapters assigned
> Assignments:
> Adapters 5 and 6
>
> Output:
> 05.
> 06.
>
> Examples 3: Only domains assigned
> Assignments:
> Domains 4 and 71 (0x47)
>
> Output:
> .0004
> .0047
I find this output to be a bit confusing; but OTOH, I'm probably not
the person to parse it :) Still, some comments.
>From previous discussions, ISTR that this is mainly supposed to be a
debugging/administration aid. Of course, this generates some questions:
- Should this be in sysfs (sysfs attributes are supposed to follow the
"one value per file" rule, at least for the most part), or would
debugfs be a better fit?
- Should userspace code be able to introspect the current
configuration? If yes, it might be better to have some
not-so-nice-but-easily-parsable output, possibly one attribute for
the assigned adapters and one for the assigned domains, and a tool
which distills that into a nice "matrix" with labeled rows and
columns for human consumption.
That said, I don't really have major objections to that interface.
>
> Signed-off-by: Tony Krowiak <akrowiak@...ux.ibm.com>
> Reviewed-by: Halil Pasic <pasic@...ux.ibm.com>
> Tested-by: Michael Mueller <mimu@...ux.ibm.com>
> Tested-by: Farhan Ali <alifm@...ux.ibm.com>
> Tested-by: Pierre Morel <pmorel@...ux.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@...ibm.com>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 52 +++++++++++++++++++++++++++++++++++++
> 1 files changed, 52 insertions(+), 0 deletions(-)
Powered by blists - more mailing lists