Am 09.09.24 um 14:41 schrieb Heiko Carstens:
On Mon, Sep 09, 2024 at 08:02:17AM -0400, Jason J. Herne wrote:
On 9/6/24 6:45 AM, Heiko Carstens wrote:
On Thu, Sep 05, 2024 at 08:43:51AM -0400, Jason J. Herne wrote:
Advertise features of the driver for the benefit of automated tooling
like Libvirt and mdevctl.
Signed-off-by: Jason J. Herne <jjherne@xxxxxxxxxxxxx>
Reviewed-by: Anthony Krowiak <akrowiak@xxxxxxxxxxxxx>
---
Documentation/arch/s390/vfio-ap.rst | 34 +++++++++++++++++++++++++++++
drivers/s390/crypto/vfio_ap_drv.c | 13 +++++++++++
2 files changed, 47 insertions(+)
Via which tree should this go upstream?
I'm not 100% sure. Would s390 next be appropriate?
Well that's up to you to decide; no objection from my side.
I think as long as we do not touch vfio internals (then we need to talk
to Alex) or kvm internals the s390 tree is a good default tree for
vfio-ap, so lets do that here.
