From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>, Amos Kong <akong@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [RFC qemu PATCH] only writing out the last byte of MAC makes it have effect
Date: Fri, 22 Mar 2013 10:45:09 +1030 [thread overview]
Message-ID: <87hak4ffxu.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130321105152.GB30874@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Thu, Mar 21, 2013 at 02:44:50PM +0800, Amos Kong wrote:
>> The lengcy guests don't have mac programming command, we don't know when
>> it's safe to use MAC. This patch changed qemu to makes MAC change effect
>> when the last byte of MAC is written to config space.
>>
>> MAC address takes first 6 bytes of config space of virtio-net, the addr
>> is 5 when the last byte is written in virtio_config_writeb().
>>
>> MAC change will effect when n->mac is updated in virtio_net_set_config().
>>
>> Signed-off-by: Amos Kong <akong@redhat.com>
>
> Let's see what Rusty says about the spec change.
Implementation notes like this belong as a footnote, eg:
For older systems, it is recommended and typical that the device
write byte 5 of the mac address last, so devices can use that as
a trigger to commit the mac address change.
Now, is this a real, or theoretical issue? Have we seen this problem in
practice, or should we continue to ignore it?
Cheers,
Rusty.
next prev parent reply other threads:[~2013-03-22 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 3:02 [Qemu-devel] [RFC virt-spec PATCH] only writing out the last byte of MAC makes it have effect Amos Kong
2013-03-21 6:44 ` [Qemu-devel] [RFC qemu " Amos Kong
2013-03-21 10:51 ` Michael S. Tsirkin
2013-03-22 0:15 ` Rusty Russell [this message]
2013-03-25 2:23 ` Amos Kong
2013-03-25 6:58 ` Michael S. Tsirkin
2013-04-08 7:05 ` Amos Kong
2013-03-21 10:53 ` [Qemu-devel] [RFC virt-spec " Michael S. Tsirkin
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=87hak4ffxu.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akong@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).