On 09/24/2018 06:10 AM, Christian Borntraeger wrote:
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next. In the future the vfio-ap driver will likely be handled by
On 09/24/2018 06:10 AM, Christian Borntraeger wrote:
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next. In the future the vfio-ap driver will likely be handled by
On 09/24/2018 07:53 AM, Cornelia Huck wrote:
On Mon, 24 Sep 2018 12:10:37 +0200
Christian Borntraeger wrote:
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next.
On 09/24/2018 07:53 AM, Cornelia Huck wrote:
On Mon, 24 Sep 2018 12:10:37 +0200
Christian Borntraeger wrote:
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next.
On 09/24/2018 07:49 AM, Cornelia Huck wrote:
On Wed, 12 Sep 2018 15:42:50 -0400
Tony Krowiak wrote:
Abstract:
On s390, we have cryptographic coprocessor cards, which are modeled on
Linux as devices on the AP bus. Each card can be partitioned into domains
which can be thought of as a
On 09/24/2018 07:49 AM, Cornelia Huck wrote:
On Wed, 12 Sep 2018 15:42:50 -0400
Tony Krowiak wrote:
Abstract:
On s390, we have cryptographic coprocessor cards, which are modeled on
Linux as devices on the AP bus. Each card can be partitioned into domains
which can be thought of as a
On Mon, 24 Sep 2018 12:10:37 +0200
Christian Borntraeger wrote:
> FWIW, assuming that review comments for v10 will be addresses in v11, I plan
> to
> add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
> after
> v11 in kvms390/next.
As said before, I think this looks
On Mon, 24 Sep 2018 12:10:37 +0200
Christian Borntraeger wrote:
> FWIW, assuming that review comments for v10 will be addresses in v11, I plan
> to
> add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
> after
> v11 in kvms390/next.
As said before, I think this looks
On Wed, 12 Sep 2018 15:42:50 -0400
Tony Krowiak wrote:
> Abstract:
>
>
> On s390, we have cryptographic coprocessor cards, which are modeled on
> Linux as devices on the AP bus. Each card can be partitioned into domains
> which can be thought of as a set of hardware registers for
On Wed, 12 Sep 2018 15:42:50 -0400
Tony Krowiak wrote:
> Abstract:
>
>
> On s390, we have cryptographic coprocessor cards, which are modeled on
> Linux as devices on the AP bus. Each card can be partitioned into domains
> which can be thought of as a set of hardware registers for
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next. In the future the vfio-ap driver will likely be handled by
Martins s390 tree, so I guess it makes sense for him
FWIW, assuming that review comments for v10 will be addresses in v11, I plan to
add the upcoming v11 to a topic branch and will merge that after 2 or 3 days
after
v11 in kvms390/next. In the future the vfio-ap driver will likely be handled by
Martins s390 tree, so I guess it makes sense for him
From: Tony Krowiak
Notes:
=
Patches 1-2 (by David) are posted with this series because they are not
currently available in our master branch, upon which this series is based,
and because this series is dependent upon them.
This patch series works with the v8 QEMU patches.
Abstract:
From: Tony Krowiak
Notes:
=
Patches 1-2 (by David) are posted with this series because they are not
currently available in our master branch, upon which this series is based,
and because this series is dependent upon them.
This patch series works with the v8 QEMU patches.
Abstract:
14 matches
Mail list logo
