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 12:05:14 +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, 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:

> Overview:
> --------
> An adjunct processor (AP) facility is an IBM Z cryptographic facility. The 
> AP facility is comprised of three AP instructions and from 1 to 256 AP 
> adapter cards. The design takes advantage of the interpretive execution mode 
> provided by the SIE architecture. With interpretive execution mode, the AP 
> instructions executed on the guest are interpreted by the hardware. This 
> allows guests direct access to AP adapter cards. The first goal of this 
> patch series is to provide direct access by a KVM guest to an AP as a 
> pass-through device. The second goal is to provide administrators with the
> means to configure KVM guests to grant direct access to AP facilities 
> assigned to the LPAR in which the host linux system is running. 
> 
> To facilitate the comprehension of the design, let's present an overview of
> the AP architecture.

I have not yet looked at the patches (and I'm not sure whether I'll be
able to do so until after the KVM Forum), but I think this also needs
some explanation under Documentation/, so people can still make sense
of it in the future.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ