From: Leonid Bloch <leonid.bloch@ravellosystems.com>
To: qemu-devel@nongnu.org
Cc: Dmitry Fleytman <dmitry@daynix.com>,
Jason Wang <jasowang@redhat.com>,
Leonid Bloch <leonid@daynix.com>,
Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
Subject: [Qemu-devel] [PATCH v6 9/9] e1000: Introducing backward compatibility command line parameter
Date: Wed, 11 Nov 2015 15:52:47 +0200 [thread overview]
Message-ID: <1447249967-10932-10-git-send-email-leonid.bloch@ravellosystems.com> (raw)
In-Reply-To: <1447249967-10932-1-git-send-email-leonid.bloch@ravellosystems.com>
This follows the previous patches, where support for migrating the
entire MAC registers' array, and some new MAC registers were introduced.
This patch introduces the e1000-specific boolean parameter
"extra_mac_registers", which is on by default. Setting it to off will
enable migration to older versions of QEMU, but will disable the read
and write access to the new registers, that were introduced since adding
the ability to migrate the entire MAC array.
Example for usage to enable backward compatibility and to disable the
new MAC registers:
qemu-system-x86_64 -device e1000,extra_mac_registers=off,... ...
As mentioned above, the default value is "on".
Signed-off-by: Leonid Bloch <leonid.bloch@ravellosystems.com>
Signed-off-by: Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>
---
hw/net/e1000.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/net/e1000.c b/hw/net/e1000.c
index 793286a..c877e06 100644
--- a/hw/net/e1000.c
+++ b/hw/net/e1000.c
@@ -1854,6 +1854,8 @@ static Property e1000_properties[] = {
compat_flags, E1000_FLAG_AUTONEG_BIT, true),
DEFINE_PROP_BIT("mitigation", E1000State,
compat_flags, E1000_FLAG_MIT_BIT, true),
+ DEFINE_PROP_BIT("extra_mac_registers", E1000State,
+ compat_flags, E1000_FLAG_MAC_BIT, true),
DEFINE_PROP_END_OF_LIST(),
};
--
2.4.3
next prev parent reply other threads:[~2015-11-11 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 13:52 [Qemu-devel] [PATCH v6 0/9] e1000: Various fixes and registers' implementation Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 1/9] e1000: Cosmetic and alignment fixes Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 2/9] e1000: Add support for migrating the entire MAC registers' array Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 3/9] e1000: Introduced an array to control the access to the MAC registers Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 4/9] e1000: Trivial implementation of various " Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 5/9] e1000: Fixing the received/transmitted packets' counters Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 6/9] e1000: Fixing the received/transmitted octets' counters Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 7/9] e1000: Fixing the packet address filtering procedure Leonid Bloch
2015-11-11 13:52 ` [Qemu-devel] [PATCH v6 8/9] e1000: Implementing various counters Leonid Bloch
2015-11-11 13:52 ` Leonid Bloch [this message]
2015-11-12 8:16 ` [Qemu-devel] [PATCH v6 0/9] e1000: Various fixes and registers' implementation Jason Wang
2015-11-12 8:35 ` Dmitry Fleytman
2015-11-12 9:45 ` Leonid Bloch
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=1447249967-10932-10-git-send-email-leonid.bloch@ravellosystems.com \
--to=leonid.bloch@ravellosystems.com \
--cc=dmitry@daynix.com \
--cc=jasowang@redhat.com \
--cc=leonid@daynix.com \
--cc=qemu-devel@nongnu.org \
--cc=shmulik.ladkani@ravellosystems.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).