From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Wang Subject: Re: [PATCH 10/12] virtio-net: multiqueue support Date: Tue, 08 Jan 2013 17:29:25 +0800 Message-ID: <50EBE6F5.9010300@redhat.com> References: <1356690724-37891-1-git-send-email-jasowang@redhat.com> <1356690724-37891-11-git-send-email-jasowang@redhat.com> <50EBE1BE.3000500@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: krkumar2@in.ibm.com, aliguori@us.ibm.com, kvm@vger.kernel.org, mst@redhat.com, mprivozn@redhat.com, rusty@rustcorp.com.au, qemu-devel@nongnu.org, stefanha@redhat.com, jwhan@filewood.snu.ac.kr, shiyer@redhat.com To: gaowanlong@cn.fujitsu.com Return-path: In-Reply-To: <50EBE1BE.3000500@cn.fujitsu.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 01/08/2013 05:07 PM, Wanlong Gao wrote: > On 12/28/2012 06:32 PM, Jason Wang wrote: >> + } else if (nc->peer->info->type != NET_CLIENT_OPTIONS_KIND_TAP) { >> + ret = -1; >> + } else { >> + ret = tap_detach(nc->peer); >> + } >> + >> + return ret; >> +} >> + >> +static void virtio_net_set_queues(VirtIONet *n) >> +{ >> + int i; >> + >> + for (i = 0; i < n->max_queues; i++) { >> + if (i < n->curr_queues) { >> + assert(!peer_attach(n, i)); >> + } else { >> + assert(!peer_detach(n, i)); > I got a assert here, > qemu-system-x86_64: /work/git/qemu/hw/virtio-net.c:330: virtio_net_set_queues: Assertion `!peer_detach(n, i)' failed. > > Any thoughts? > > Thanks, > Wanlong Gao Thanks for the testing, which steps or cases did you met this assertion, migration, reboot or just changing the number of virtqueues? >> + } >> + } >> +} >> + >> +static void virtio_net_set_multiqueue(VirtIONet *n, int multiqueue, int ctrl); >> + > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html