From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yn679-0008W7-Kd for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:04:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yn674-0003zi-V7 for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:03:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52811) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yn674-0003zH-M3 for qemu-devel@nongnu.org; Tue, 28 Apr 2015 10:03:50 -0400 Date: Tue, 28 Apr 2015 16:03:37 +0200 From: "Michael S. Tsirkin" Message-ID: <20150428160323-mutt-send-email-mst@redhat.com> References: <1430221873-5788-1-git-send-email-shannon.zhao@linaro.org> <20150428144735-mutt-send-email-mst@redhat.com> <20150428150426-mutt-send-email-mst@redhat.com> <20150428152054.3a84658c.cornelia.huck@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150428152054.3a84658c.cornelia.huck@de.ibm.com> Subject: Re: [Qemu-devel] [PATCH v4 0/2] virtio: Move host features to backends List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: Peter Maydell , hangaohuai@huawei.com, "Huangpeng (Peter)" , QEMU Developers , Shannon Zhao , Shannon Zhao , Paolo Bonzini , Christoffer Dall On Tue, Apr 28, 2015 at 03:20:54PM +0200, Cornelia Huck wrote: > On Tue, 28 Apr 2015 15:05:47 +0200 > "Michael S. Tsirkin" wrote: > > > On Tue, Apr 28, 2015 at 01:52:40PM +0100, Peter Maydell wrote: > > > On 28 April 2015 at 13:48, Michael S. Tsirkin wrote: > > > > On Tue, Apr 28, 2015 at 07:51:11PM +0800, shannon.zhao@linaro.org wrote: > > > >> From: Shannon Zhao > > > >> Here we move the host features to backends, involving > > > >> DEFINE_VIRTIO_NET_FEATURES, DEFINE_VIRTIO_SCSI_FEATURES. So the > > > >> virtio-mmio devices could have the host freatures, and this has a great > > > >> performance improvement to virtio-mmio, especially to virtio-net-device. > > > > > > > > Can you move COMMON_FEATURES too please? > > > > > > I think that would be wrong -- COMMON_FEATURES are transport features, > > > not backend-specific features, so they belong on the transports > > > (and on the convenience wrappers), not the backends. > > > > > > thanks > > > -- PMM > > > > Hmm you are right. The problem is with s390 which > > puts this DEFINE_VIRTIO_COMMON_FEATURES in all devices. > > All save virtio-blk. There were some problems when switching on > event_idx on virtio-blk, IIRC. Specifically on s390? > The other transport add DEFINE_VIRTIO_COMMON FEATURES in their base > class. Because of the not-quite-understood problem with virtio-blk, we > couldn't do that with s390-virtio. -- MST