From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Wang Subject: Re: [PATCH 1/2] virito: introduce methods of fixing device features Date: Wed, 26 Nov 2014 02:09:00 -0500 (EST) Message-ID: <848153913.16119602.1416985740195.JavaMail.zimbra@redhat.com> References: <1415857974-23326-1-git-send-email-jasowang@redhat.com> <87sih9xv5u.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87sih9xv5u.fsf@rustcorp.com.au> 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: Rusty Russell Cc: netdev@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, mst@redhat.com List-Id: virtualization@lists.linuxfoundation.org ----- Original Message ----- > Jason Wang writes: > > Buggy host may advertised buggy host features (a usual case is that host > > advertise a feature whose dependencies were missed). In this case, driver > > should detect and disable the buggy features by itself. > > Sorry, I've been focussing elsewhere. > > I would really prefer that drivers offer a "feature_depends" table, > which can indicate that feature A depends on feature B, and have the > core iterate, complain and fixup as necessary. > > Is that expressive enough, or do we need more? > > Thanks, > Rusty. I suggested something like this in https://lkml.org/lkml/2014/11/19/132, but Michael does not like it ...