From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelia Huck Subject: Re: [PATCH RFC v6 18/20] virtio: support revision-specific features Date: Wed, 7 Jan 2015 17:22:32 +0100 Message-ID: <20150107172232.57cbeb31.cornelia.huck@de.ibm.com> References: <1418304322-7546-1-git-send-email-cornelia.huck@de.ibm.com> <1418304322-7546-19-git-send-email-cornelia.huck@de.ibm.com> <20141228083206.GA6802@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141228083206.GA6802@redhat.com> 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: "Michael S. Tsirkin" Cc: thuth@linux.vnet.ibm.com, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org List-Id: virtualization@lists.linuxfoundation.org On Sun, 28 Dec 2014 10:32:06 +0200 "Michael S. Tsirkin" wrote: > On Thu, Dec 11, 2014 at 02:25:20PM +0100, Cornelia Huck wrote: > > Devices may support different sets of feature bits depending on which > > revision they're operating at. Let's give the transport a way to > > re-query the device about its features when the revision has been > > changed. > > > > Signed-off-by: Cornelia Huck > > So now we have both get_features and get_features_rev, and > it's never clear which revision does host_features refer to. > IMHO that's just too messy. > Let's add get_legacy_features and host_legacy_features instead? I wanted to avoid touching anything that does not support version 1. And this interface might still work for later revisions, no?