From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH 1/3] virtio: find_vqs/del_vqs virtio operations Date: Sun, 10 May 2009 10:25:38 +0300 Message-ID: <20090510072538.GA5335__33920.1830830008$1241940618$gmane$org@redhat.com> References: <200905081637.09729.rusty@rustcorp.com.au> <20090508124821.GA3073@redhat.com> <200905101337.06836.rusty@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <200905101337.06836.rusty@rustcorp.com.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Rusty Russell Cc: Christian Borntraeger , avi@redhat.com, kvm@vger.kernel.org, Anthony Liguori , virtualization@lists.linux-foundation.org List-Id: virtualization@lists.linuxfoundation.org On Sun, May 10, 2009 at 01:37:06PM +0930, Rusty Russell wrote: > Yes, and in fact a rough look at your patch reveals that we don't actually > need del_vq: now we track them, we can just do that as part of vdev > destruction, right? Let's assume that a driver encounters an error in probe after it calls find_vq. It would need a way to revert find_vq, won't it? It seems to me that bus->remove does not get called on probe failure. Isn't that right? -- MST