From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: [PATCH 0/2] virtio: recover from vector assignment failure Date: Thu, 23 Jul 2009 18:45:22 +0300 Message-ID: <20090723154522.GA13965@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Christian Borntraeger , virtualization@lists.linux-foundation.org, Anthony Liguori , kvm@vger.kernel.org, avi@redhat.com, Carsten Otte < Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57777 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753140AbZGWPq2 (ORCPT ); Thu, 23 Jul 2009 11:46:28 -0400 Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: This patch series fixes a regression reported by Amit Shah (see Subject: Re: qemu-kvm missing some msix capability check, Message-Id: 20090723142550.GA4470@amit-x200.redhat.com) Since Amit's testing, I have refactored the change slightly to make the patch smaller. Rusty, can this go in for 2.6.31, or do you think it's too big a change? As an alternative work-around, we possibly could do something in qemu in host to make it less likely that mapping vq to vector fails - but it seems that we still want the guest to handle the error as gracefully as possible, right? -- MST Michael S. Tsirkin (2): virtio: delete vq from list virtio: retry on vector assignment failure drivers/virtio/virtio_pci.c | 136 ++++++++++++++++++++++++------------------- 1 files changed, 76 insertions(+), 60 deletions(-)