lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 16 Oct 2017 11:27:55 +0200
From:   Martin Schwidefsky <schwidefsky@...ibm.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, heiko.carstens@...ibm.com,
        borntraeger@...ibm.com, cohuck@...hat.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,
        qemu-s390x@...gnu.org, jjherne@...ux.vnet.ibm.com,
        thuth@...hat.com, pasic@...ux.vnet.ibm.com
Subject: Re: [RFC 00/19] KVM: s390/crypto/vfio: guest dedicated crypto
 adapters

On Fri, 13 Oct 2017 13:38:45 -0400
Tony Krowiak <akrowiak@...ux.vnet.ibm.com> wrote:

> Tony Krowiak (19):
>   KVM: s390: SIE considerations for AP Queue virtualization
>   KVM: s390: refactor crypto initialization
>   s390/zcrypt: new AP matrix bus
>   s390/zcrypt: create an AP matrix device on the AP matrix bus
>   s390/zcrypt: base implementation of AP matrix device driver
>   s390/zcrypt: register matrix device with VFIO mediated device
>     framework
>   KVM: s390: introduce AP matrix configuration interface
>   s390/zcrypt: support for assigning adapters to matrix mdev
>   s390/zcrypt: validate adapter assignment
>   s390/zcrypt: sysfs interfaces supporting AP domain assignment
>   s390/zcrypt: validate domain assignment
>   s390/zcrypt: sysfs support for control domain assignment
>   s390/zcrypt: validate control domain assignment
>   KVM: s390: Connect the AP mediated matrix device to KVM
>   s390/zcrypt: introduce ioctl access to VFIO AP Matrix driver
>   KVM: s390: interface to configure KVM guest's AP matrix
>   KVM: s390: validate input to AP matrix config interface
>   KVM: s390: New ioctl to configure KVM guest's AP matrix
>   s390/facilities: enable AP facilities needed by guest

Overall I am quite happy with the patches, only minor things I would
like to see improved. We have to agree how we want to approach the
upstream process between my s390/linux tree and the s390/kvm tree.
Probably a tip branch again for the both tress to pull from.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ