On 21/02/2019 14:01, Christian Borntraeger wrote:
On 21.02.2019 13:51, Pierre Morel wrote:
On 21/02/2019 13:35, Christian Borntraeger wrote:
[..]
Go ahead and send this as v3?
OK
CC stable ?
Yes, also add a "Fixes:" tag.
Yes, I will not forget this time :)
Thanks
Pierre
--
Pierre
On 21.02.2019 13:51, Pierre Morel wrote:
> On 21/02/2019 13:35, Christian Borntraeger wrote:
>>
>>
[..]
>> Go ahead and send this as v3?
>>
>
> OK
> CC stable ?
Yes, also add a "Fixes:" tag.
On 21/02/2019 13:35, Christian Borntraeger wrote:
On 21.02.2019 13:10, Pierre Morel wrote:
On 20/02/2019 13:51, Halil Pasic wrote:
On Wed, 20 Feb 2019 10:27:31 +0100
Cornelia Huck wrote:
On Tue, 19 Feb 2019 22:31:17 +0100
Pierre Morel wrote:
On 19/02/2019 19:52, Tony Krowiak wrote:
On
On 21.02.2019 13:10, Pierre Morel wrote:
> On 20/02/2019 13:51, Halil Pasic wrote:
>> On Wed, 20 Feb 2019 10:27:31 +0100
>> Cornelia Huck wrote:
>>
>>> On Tue, 19 Feb 2019 22:31:17 +0100
>>> Pierre Morel wrote:
>>>
On 19/02/2019 19:52, Tony Krowiak wrote:
> On 2/18/19 1:08 PM, Pierre
On 20/02/2019 13:51, Halil Pasic wrote:
On Wed, 20 Feb 2019 10:27:31 +0100
Cornelia Huck wrote:
On Tue, 19 Feb 2019 22:31:17 +0100
Pierre Morel wrote:
On 19/02/2019 19:52, Tony Krowiak wrote:
On 2/18/19 1:08 PM, Pierre Morel wrote:
Libudev relies on having a subsystem link for non-root de
On 19/02/2019 10:44, Christian Borntraeger wrote:
On 19.02.2019 10:22, Cornelia Huck wrote:
On Mon, 18 Feb 2019 19:08:48 +0100
Pierre Morel wrote:
...snip...
+static struct bus_type matrix_bus = {
+ .name = "vfio_ap",
+ .match = &matrix_bus_match,
+};
+
+static int matrix_pro
On 21/02/2019 08:37, Christian Borntraeger wrote:
On 20.02.2019 14:12, Harald Freudenberger wrote:
On 18.02.19 19:08, Pierre Morel wrote:
Libudev relies on having a subsystem link for non-root devices. To
avoid libudev (and potentially other userspace tools) choking on the
matrix device let u
On 21.02.19 08:37, Christian Borntraeger wrote:
>
> On 20.02.2019 14:12, Harald Freudenberger wrote:
>> On 18.02.19 19:08, Pierre Morel wrote:
>>> Libudev relies on having a subsystem link for non-root devices. To
>>> avoid libudev (and potentially other userspace tools) choking on the
>>> matrix d
On 20.02.2019 14:12, Harald Freudenberger wrote:
> On 18.02.19 19:08, Pierre Morel wrote:
>> Libudev relies on having a subsystem link for non-root devices. To
>> avoid libudev (and potentially other userspace tools) choking on the
>> matrix device let us introduce a vfio_ap bus and with that th
On 18.02.19 19:08, Pierre Morel wrote:
> Libudev relies on having a subsystem link for non-root devices. To
> avoid libudev (and potentially other userspace tools) choking on the
> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
> bus subsytem, and make the matrix device resi
On Wed, 20 Feb 2019 10:27:31 +0100
Cornelia Huck wrote:
> On Tue, 19 Feb 2019 22:31:17 +0100
> Pierre Morel wrote:
>
> > On 19/02/2019 19:52, Tony Krowiak wrote:
> > > On 2/18/19 1:08 PM, Pierre Morel wrote:
> > >> Libudev relies on having a subsystem link for non-root devices. To
> > >> avoi
On Tue, 19 Feb 2019 22:31:17 +0100
Pierre Morel wrote:
> On 19/02/2019 19:52, Tony Krowiak wrote:
> > On 2/18/19 1:08 PM, Pierre Morel wrote:
> >> Libudev relies on having a subsystem link for non-root devices. To
> >> avoid libudev (and potentially other userspace tools) choking on the
> >> ma
On 19/02/2019 19:52, Tony Krowiak wrote:
On 2/18/19 1:08 PM, Pierre Morel wrote:
Libudev relies on having a subsystem link for non-root devices. To
avoid libudev (and potentially other userspace tools) choking on the
matrix device let us introduce a vfio_ap bus and with that the vfio_ap
bus subs
On 2/18/19 1:08 PM, Pierre Morel wrote:
Libudev relies on having a subsystem link for non-root devices. To
avoid libudev (and potentially other userspace tools) choking on the
matrix device let us introduce a vfio_ap bus and with that the vfio_ap
bus subsytem, and make the matrix device reside wi
On Mon, 18 Feb 2019 19:08:48 +0100
Pierre Morel wrote:
> Libudev relies on having a subsystem link for non-root devices. To
> avoid libudev (and potentially other userspace tools) choking on the
> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
> bus subsytem, and make the
On 19.02.2019 10:22, Cornelia Huck wrote:
> On Mon, 18 Feb 2019 19:08:48 +0100
> Pierre Morel wrote:
>
>> Libudev relies on having a subsystem link for non-root devices. To
>> avoid libudev (and potentially other userspace tools) choking on the
>> matrix device let us introduce a vfio_ap bus a
On Mon, 18 Feb 2019 19:08:48 +0100
Pierre Morel wrote:
> Libudev relies on having a subsystem link for non-root devices. To
> avoid libudev (and potentially other userspace tools) choking on the
> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
> bus subsytem, and make the
On 18.02.2019 19:08, Pierre Morel wrote:
> Libudev relies on having a subsystem link for non-root devices. To
> avoid libudev (and potentially other userspace tools) choking on the
> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
> bus subsytem, and make the matrix device
Libudev relies on having a subsystem link for non-root devices. To
avoid libudev (and potentially other userspace tools) choking on the
matrix device let us introduce a vfio_ap bus and with that the vfio_ap
bus subsytem, and make the matrix device reside within it.
Doing this we need to suppress t
19 matches
Mail list logo
