qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: somlo@cmu.edu, marcel.a@redhat.com, jasowang@redhat.com,
	stefanha@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] ignore bus master for e1000
Date: Thu, 18 Dec 2014 17:22:17 +0800	[thread overview]
Message-ID: <1418894539-13990-1-git-send-email-akong@redhat.com> (raw)

Win2012-64r2 guest doesn't set bus mastering correctly,
it caused guest network down, this patch ignored it for
e1000 nic for workarounding the guest issue.

Patch 1 is an update version of:
http://lists.gnu.org/archive/html/qemu-devel/2014-12/msg00048.html
transmit packets are also defered in latest version.

Amos Kong (1):
  e1000: unconditionally enable bus mastering

Michael S. Tsirkin (1):
  e1000: defer packets until BM enabled

 hw/net/e1000.c | 34 +++++++++++++++++++++++++++++++++-
 1 file changed, 33 insertions(+), 1 deletion(-)

-- 
2.1.0

             reply	other threads:[~2014-12-18  9:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18  9:22 Amos Kong [this message]
2014-12-18  9:22 ` [Qemu-devel] [PATCH 1/2] e1000: defer packets until BM enabled Amos Kong
2014-12-18  9:22 ` [Qemu-devel] [PATCH 2/2] e1000: unconditionally enable bus mastering Amos Kong
2014-12-18  9:49   ` Jason Wang
2014-12-18 10:30     ` Amos Kong
2015-01-07 16:08   ` Stefan Hajnoczi
2015-02-06 13:46     ` Stefan Hajnoczi
2015-02-10 16:11       ` Amos Kong
2014-12-18 10:05 ` [Qemu-devel] [PATCH 0/2] ignore bus master for e1000 Jason Wang
2014-12-18 11:01   ` Denis V. Lunev
2014-12-18 11:11     ` Denis V. Lunev
2014-12-19  4:59       ` Jason Wang
2014-12-19  3:09   ` Amos Kong
2014-12-19  5:00     ` 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=1418894539-13990-1-git-send-email-akong@redhat.com \
    --to=akong@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=somlo@cmu.edu \
    --cc=stefanha@redhat.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 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).