From: Jason Wang <jasowang@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH 1/2] virito: introduce methods of fixing device features
Date: Wed, 26 Nov 2014 02:09:00 -0500 (EST) [thread overview]
Message-ID: <848153913.16119602.1416985740195.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <87sih9xv5u.fsf@rustcorp.com.au>
----- Original Message -----
> Jason Wang <jasowang@redhat.com> 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 ...
next prev parent reply other threads:[~2014-11-26 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 5:52 [PATCH 1/2] virito: introduce methods of fixing device features Jason Wang
2014-11-13 5:52 ` [PATCH 2/2] virtio-net: fix buggy features advertised by host Jason Wang
2014-11-13 6:06 ` Wanlong Gao
2014-11-13 6:45 ` Jason Wang
2014-11-13 8:53 ` Cornelia Huck
2014-11-13 9:12 ` Jason Wang
2014-11-13 8:46 ` [PATCH 1/2] virito: introduce methods of fixing device features Cornelia Huck
2014-11-13 9:11 ` Jason Wang
2014-11-13 9:14 ` Cornelia Huck
2014-11-13 9:49 ` Jason Wang
2014-11-24 1:08 ` Rusty Russell
2014-11-26 7:09 ` Jason Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 5:24 Jason Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=848153913.16119602.1416985740195.JavaMail.zimbra@redhat.com \
--to=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).