From: Vlad Yasevich <vyasevic@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vlad Yasevich <vyasevic@redhat.com>,
alex.williamson@redhat.com, akong@redhat.com,
stefanha@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [RFC PATCH 0/2] Update HMP only upon mac change completion.
Date: Thu, 21 Nov 2013 15:04:18 -0500 [thread overview]
Message-ID: <1385064260-20962-1-git-send-email-vyasevic@redhat.com> (raw)
Recent threads regarding e1000/rtl8139 and mac address change notifications
prompted some research into the respecitive hw data sheets as well as
available drivers. What I found is that each hw has a mechanism that
can be used by our emulation layer to determine when the mac address
change has completed (when the OS finished writing the mac address),
and we can use these mechanisms to trigger HMP notifications.
This is only an RFC series. It's been tested and works well.
I've split e1000 and rtl8139 changes as they are sufficiently
different. e1000 make this very clean and easy, but rtl8139
isn't as nice.
Please take a look and I'd like to hear your comments.
Thanks
-vlad
Vlad Yasevich (2):
e1000: Use Address_Available bit as HW latch
rtl8139: update HMP only when the address is fully written
hw/i386/pc_piix.c | 4 ++++
hw/i386/pc_q35.c | 4 ++++
hw/net/e1000.c | 11 ++++++++++-
hw/net/rtl8139.c | 50 +++++++++++++++++++++++++++++++++++++++++++++++++-
include/hw/i386/pc.h | 8 ++++++++
5 files changed, 75 insertions(+), 2 deletions(-)
--
1.8.4.2
next reply other threads:[~2013-11-21 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 20:04 Vlad Yasevich [this message]
2013-11-21 20:04 ` [Qemu-devel] [RFC PATCH 1/2] e1000: Use Address_Available bit as HW latch Vlad Yasevich
2013-11-21 21:15 ` Eric Blake
2013-11-22 9:47 ` Jason Wang
2013-11-22 14:37 ` Vlad Yasevich
2013-11-25 9:23 ` Jason Wang
2013-11-21 20:04 ` [Qemu-devel] [RFC PATCH 2/2] rtl8139: update HMP only when the address is fully written Vlad Yasevich
2013-11-21 21:18 ` Eric Blake
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=1385064260-20962-1-git-send-email-vyasevic@redhat.com \
--to=vyasevic@redhat.com \
--cc=akong@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).