On 12/03/2019 22:39, Tony Krowiak wrote:
On 3/3/19 9:09 PM, Halil Pasic wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and
On 3/3/19 9:09 PM, Halil Pasic wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
[..]
+static int
On 3/3/19 9:09 PM, Halil Pasic wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
[..]
+static int
On 04/03/2019 03:09, Halil Pasic wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
[..]
+static
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
> We need to associate the ap_vfio_queue, which will hold the
> per queue information for interrupt with a matrix mediated device
> which hold the configuration and the way to the CRYCB.
[..]
> +static int vfio_ap_get_all_domains(struct
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a APID or a APQI to the mediated device
and
On 2/27/19 4:29 AM, Pierre Morel wrote:
On 26/02/2019 19:14, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to
On 27/02/2019 10:32, Cornelia Huck wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this
On 27/02/2019 10:32, Cornelia Huck wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
> We need to associate the ap_vfio_queue, which will hold the
> per queue information for interrupt with a matrix mediated device
> which hold the configuration and the way to the CRYCB.
>
> Let's do this when assigning a APID or a APQI to
On 26/02/2019 19:14, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a
On 2/22/19 10:29 AM, Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a APID or a APQI to the mediated device
and
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
Let's do this when assigning a APID or a APQI to the mediated device
and clear the relation when unassigning.
13 matches
Mail list logo
