search for: a9rez

Displaying 11 results from an estimated 11 matches for "a9rez".

2020 Feb 11
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...uld you try this patch on top of eccb852f1fe6bede630e2e4f1a121a81e34354ab? I still get [ 43.665145] Guest moved used index from 0 to 289 after some reboots. > > Thanks! > > From 71d0f9108a18aa894cc0c0c1c7efbad39f465a27 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= < > eperezma at redhat.com> > Date: Tue, 11 Feb 2020 13:19:10 +0100 > Subject: [PATCH] vhost: fix return value of vhost_get_vq_desc > > Before of the batch change, it was the chain's head. Need to keep that > way or we will not be able to free a chain of descriptors....
2020 Feb 11
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...> > Hi Christian. Thank you very much for your fast responses. > > Could you try this patch on top of eccb852f1fe6bede630e2e4f1a121a81e34354ab? > > Thanks! > > >From 71d0f9108a18aa894cc0c0c1c7efbad39f465a27 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= < > eperezma at redhat.com> > Date: Tue, 11 Feb 2020 13:19:10 +0100 > Subject: [PATCH] vhost: fix return value of vhost_get_vq_desc > > Before of the batch change, it was the chain's head. Need to keep that > way or we will not be able to free a chain of descriptors....
2020 Feb 13
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...gt;> >> I still get >> [ 43.665145] Guest moved used index from 0 to 289 >> after some reboots. >> >> >>> Thanks! >>> >>> From 71d0f9108a18aa894cc0c0c1c7efbad39f465a27 Mon Sep 17 00:00:00 2001 >>> From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= < >>> eperezma at redhat.com> >>> Date: Tue, 11 Feb 2020 13:19:10 +0100 >>> Subject: [PATCH] vhost: fix return value of vhost_get_vq_desc >>> >>> Before of the batch change, it was the chain's head. Need to keep that >>> way or we wi...
2020 Feb 06
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...> > It will not solve your first random crash but it should help with the lost of network connectivity. > > Please let me know how does it goes. > > Thanks! > > >From 99f0f543f3939dbe803988c9153a95616ccccacd Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= <eperezma at redhat.com> > Date: Thu, 6 Feb 2020 15:13:42 +0100 > Subject: [PATCH] vhost: filter valid vhost descriptors flags > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > Previous commit copy _NEXT flag, and it co...
2020 Feb 13
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 13.02.20 17:29, Eugenio P?rez wrote: > Can we try with this traces? Does not apply on eccb852f1fe6bede630e2e4f1a121a81e34354ab, can you double check? > > From b793b4106085ab1970bdedb340e49f37843ed585 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= <eperezma at redhat.com> > Date: Thu, 13 Feb 2020 17:27:05 +0100 > Subject: [PATCH] vhost: Add debug in ioctl calls > > --- > drivers/vhost/net.c | 20 +++++++++++++++++--- > drivers/vhost/vhost.c | 16 ++++++++++++++-- > 2 files changed, 31 insertions(+), 5 deletio...
2020 Feb 14
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...Sorry, that was meant to be applied over previous debug patch. > > Here I inline the one meant to be applied over eccb852f1fe6bede630e2e4f1a121a81e34354ab. > > Thanks! > > From d978ace99e4844b49b794d768385db3d128a4cc0 Mon Sep 17 00:00:00 2001 > From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= <eperezma at redhat.com> > Date: Fri, 14 Feb 2020 08:02:26 +0100 > Subject: [PATCH] vhost: disable all features and trace last_avail_idx and > ioctl calls > > --- > drivers/vhost/net.c | 20 +++++++++++++++++--- > drivers/vhost/vhost.c | 25 +++++++++++++++++++++++-...
2020 Feb 14
0
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
...ug patch. >>> >>> Here I inline the one meant to be applied over eccb852f1fe6bede630e2e4f1a121a81e34354ab. >>> >>> Thanks! >>> >>> From d978ace99e4844b49b794d768385db3d128a4cc0 Mon Sep 17 00:00:00 2001 >>> From: =?UTF-8?q?Eugenio=20P=C3=A9rez?= <eperezma at redhat.com> >>> Date: Fri, 14 Feb 2020 08:02:26 +0100 >>> Subject: [PATCH] vhost: disable all features and trace last_avail_idx and >>> ioctl calls >>> >>> --- >>> drivers/vhost/net.c | 20 +++++++++++++++++--- >>&g...
2020 Jan 07
6
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 07.01.20 10:39, Michael S. Tsirkin wrote: > On Tue, Jan 07, 2020 at 09:59:16AM +0100, Christian Borntraeger wrote: >> >> >> On 06.01.20 11:50, Michael S. Tsirkin wrote: >>> On Wed, Dec 18, 2019 at 04:59:02PM +0100, Christian Borntraeger wrote: >>>> On 18.12.19 16:10, Michael S. Tsirkin wrote: >>>>> On Wed, Dec 18, 2019 at 03:43:43PM
2020 Jan 07
6
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On 07.01.20 10:39, Michael S. Tsirkin wrote: > On Tue, Jan 07, 2020 at 09:59:16AM +0100, Christian Borntraeger wrote: >> >> >> On 06.01.20 11:50, Michael S. Tsirkin wrote: >>> On Wed, Dec 18, 2019 at 04:59:02PM +0100, Christian Borntraeger wrote: >>>> On 18.12.19 16:10, Michael S. Tsirkin wrote: >>>>> On Wed, Dec 18, 2019 at 03:43:43PM
2020 Feb 07
16
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On Fri, Feb 07, 2020 at 08:47:14AM +0100, Christian Borntraeger wrote: > Also adding Cornelia. > > > On 06.02.20 23:17, Michael S. Tsirkin wrote: > > On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > >> > >> > >> On 06.02.20 15:22, eperezma at redhat.com wrote: > >>> Hi Christian. > >>> > >>>
2020 Feb 07
16
vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
On Fri, Feb 07, 2020 at 08:47:14AM +0100, Christian Borntraeger wrote: > Also adding Cornelia. > > > On 06.02.20 23:17, Michael S. Tsirkin wrote: > > On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > >> > >> > >> On 06.02.20 15:22, eperezma at redhat.com wrote: > >>> Hi Christian. > >>> > >>>