From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2xoW-0004mp-Uc for qemu-devel@nongnu.org; Thu, 11 Jun 2015 04:26:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z2xoW-0004gm-1Q for qemu-devel@nongnu.org; Thu, 11 Jun 2015 04:26:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z2xoV-0004g0-S2 for qemu-devel@nongnu.org; Thu, 11 Jun 2015 04:26:15 -0400 Message-ID: <1434011172.27114.25.camel@redhat.com> From: Gerd Hoffmann Date: Thu, 11 Jun 2015 10:26:12 +0200 In-Reply-To: <20150604125203-mutt-send-email-mst@redhat.com> References: <1433414083-9720-1-git-send-email-kraxel@redhat.com> <20150604125203-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/33] virtio 1.0 patch series rebased List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Cornelia Huck , qemu-devel@nongnu.org Hi, > Here's an incomplete todo for spec compliance: note that it does not > have to block this patchset: > - complete other devices besides net, balloon > need to disable a bunch of features > that 1.0 has deprecated So, what is the plan here? For legacy devices we keep the features, for backward compatibility reasons. For modern devices we drop the deprecated features. What about transitional? Drop them too? Implementation-wise we probably want a mask in VirtIODevice ... cheers, Gerd