From: "Michael S. Tsirkin" <mst@redhat.com>
To: "houyl@yusur.tech" <houyl@yusur.tech>
Cc: jasowang <jasowang@redhat.com>,
"raphael.norwitz" <raphael.norwitz@nutanix.com>,
kwolf <kwolf@redhat.com>, hreitz <hreitz@redhat.com>,
qemu-block <qemu-block@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>, zy <zy@yusur.tech>,
"lulu@redhat.com" <lulu@redhat.com>, 陈浩 <chenh@yusur.tech>
Subject: Re: Re: [PATCH v2] hw/virtio/vhost-user: support obtain vdpa device's mac address automatically
Date: Fri, 23 Sep 2022 02:20:24 -0400 [thread overview]
Message-ID: <20220923021957-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2022092311532239888519@yusur.tech>
On Fri, Sep 23, 2022 at 11:53:22AM +0800, houyl@yusur.tech wrote:
> On Thu, 22 Sep 2022 09:34:41 +0800 Jason Wang<jasowang@redhat.com> wrote:
>
>
> >On Thu, Sep 22, 2022 at 1:58 AM Raphael Norwitz
> ><raphael.norwitz@nutanix.com> wrote:
> >>
> >> If I read your response on the other thread correctly, this change is
> intended
> >>
> >> to prioritize the MAC address exposed by DPDK over the one provided by
> the
> >>
> >> QEMU command line? Sounds reasonable in principle, but I would get
> confirmation
> >>
> >> from vDPA/vhost-net maintainers.
>
> >I think the best way is to (and it seems easier)
>
> >1) have the management layer to make sure the mac came from cli
> >matches the underlayer vDPA
>
> Agreed, that's no problem.
>
> >2) having a sanity check and fail the device initialization if they don't
> match
>
> However, one MAC address for integrity check is from the cli, and the other
> MAC address is from the vDPA device,
> How to get it?
>
> The current situation is if MAC came from cli don't match the underlayer
> vDPA, the virtual machine can still start without any hints.
>
> Thanks
>
>
Let me ask then, why are you supplying the incorrect MAC on the cli?
--
MST
next prev parent reply other threads:[~2022-09-23 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:00 [PATCH v2] hw/virtio/vhost-user: support obtain vdpa device's mac address automatically chenh
2022-09-21 17:56 ` Raphael Norwitz
2022-09-22 1:34 ` Jason Wang
2022-09-22 9:56 ` Michael S. Tsirkin
2022-09-23 3:21 ` 陈浩
2022-09-23 3:36 ` Jason Wang
2022-09-23 3:53 ` houyl
2022-09-23 4:05 ` Jason Wang
2022-09-23 6:19 ` Michael S. Tsirkin
2022-09-23 6:20 ` Michael S. Tsirkin [this message]
2022-09-21 18:23 ` Alex Bennée
2022-09-21 19:24 ` Michael S. Tsirkin
2022-09-22 10:02 ` Alex Bennée
2022-09-22 10:19 ` Michael S. Tsirkin
2022-09-23 3:30 ` 陈浩
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=20220923021957-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=chenh@yusur.tech \
--cc=houyl@yusur.tech \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=lulu@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=zy@yusur.tech \
/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).