From: John <jw@nuclearfallout.net>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] xen-netback: make feature-rx-notify mandatory -- Breaks stubdoms
Date: Wed, 17 Dec 2014 15:29:38 -0800 [thread overview]
Message-ID: <549211E2.8030901@nuclearfallout.net> (raw)
In-Reply-To: <54918C89.1020409@citrix.com>
On 12/17/2014 6:00 AM, David Vrabel wrote:
> This patch works for me. I tested it with a hacked Linux frontend that
> disabled feature-rx-notify, but not with a stubdom.
>
> Can you give it a try, please?
I tested this and it does seem to work -- at least, a stubdom-based domU
starts up and runs properly. That said, I'm not using the minios network
functionality much, since all of my customer and test domains use PVHVM
drivers.
-John
next prev parent reply other threads:[~2014-12-17 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54884DA8.7030003@nuclearfallout.net>
2014-12-10 14:12 ` xen-netback: make feature-rx-notify mandatory -- Breaks stubdoms David Vrabel
2014-12-10 15:07 ` Ian Campbell
2014-12-10 15:07 ` Ian Campbell
2014-12-10 15:29 ` David Vrabel
2014-12-10 15:29 ` David Vrabel
2014-12-10 16:20 ` Ian Campbell
2014-12-10 16:20 ` Ian Campbell
2014-12-10 18:39 ` David Vrabel
2014-12-10 18:39 ` David Vrabel
2014-12-17 14:00 ` [Xen-devel] " David Vrabel
2014-12-17 23:29 ` John
2014-12-17 23:29 ` John [this message]
2014-12-17 14:00 ` David Vrabel
2014-12-10 14:12 ` David Vrabel
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=549211E2.8030901@nuclearfallout.net \
--to=jw@nuclearfallout.net \
--cc=Xen-devel@lists.xen.org \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.