From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HR7-00075L-DS for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:02:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V2HR4-0000km-Qt for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:02:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HR4-0000kf-IQ for qemu-devel@nongnu.org; Thu, 25 Jul 2013 05:02:10 -0400 Date: Thu, 25 Jul 2013 12:03:17 +0300 From: "Michael S. Tsirkin" Message-ID: <20130725090317.GA26648@redhat.com> References: <1373661422-23606-1-git-send-email-peter.maydell@linaro.org> <1373661422-23606-4-git-send-email-peter.maydell@linaro.org> <20130725053841.GA15500@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2 3/8] virtio: Add support for guest setting of queue size List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Anthony Liguori , patches@linaro.org, Alexander Graf , qemu-devel@nongnu.org, kvmarm@lists.cs.columbia.edu, David Gibson On Thu, Jul 25, 2013 at 09:50:21AM +0100, Peter Maydell wrote: > On 25 July 2013 06:38, Michael S. Tsirkin wrote: > > On Fri, Jul 12, 2013 at 09:36:57PM +0100, Peter Maydell wrote: > >> The MMIO virtio transport spec allows the guest to tell the host how > >> large the queue size is. Add virtio_queue_set_num() function which > >> implements this in the QEMU common virtio support code. > >> > >> Signed-off-by: Peter Maydell > > > > Probably needs to go back to default value on reset? > > Tricky, since the default value is "whatever was passed to > virtio_add_queue()" and we don't save that anywhere. > > For virtio-mmio it is a guest bug to fail to write to the > QueueNum register, so the current behaviour is not out of > specification (and not harmful either AFAICT). Best not to leak info across reboots. Also if guest sets num = 0 it will cause all kind of harm, no? > I guess we could add a vring.defaultnum, which would be > set by virtio_add_queue/virtio_del_queue, and have reset > copy defaultnum into num. No migration needed for defaultnum > because it's always the same for a particular qemu config. Sounds good. > > Need to migrate? > > It's already migrated (though I'm not entirely sure why). > > > Is the default value a max legal value? If yes probably a good > > idea to enforce this. > > virtio_add_queue() already enforces this -- it will abort() > if you try to set up a queue with a default size greater > than VIRTQUEUE_MAX_SIZE. No I mean does default value have some meaning? Does host supply a hint of a max value besides VIRTQUEUE_MAX_SIZE? > > thanks > -- PMM