[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240617094421.4ae387d7@kernel.org>
Date: Mon, 17 Jun 2024 09:44:21 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Parav Pandit <parav@...dia.com>, Jason
Wang <jasowang@...hat.com>, Cindy Lu <lulu@...hat.com>, Dragos Tatulea
<dtatulea@...dia.com>, "virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/2] vdpa: support set mac address from vdpa tool
On Mon, 17 Jun 2024 12:20:19 -0400 Michael S. Tsirkin wrote:
> > But the virtio spec doesn't allow setting the MAC...
> > I'm probably just lost in the conversation but there's hypervisor side
> > and there is user/VM side, each of them already has an interface to set
> > the MAC. The MAC doesn't matter, but I want to make sure my mental model
> > matches reality in case we start duplicating too much..
>
> An obvious part of provisioning is specifying the config space
> of the device.
Agreed, that part is obvious.
Please go ahead, I don't really care and you clearly don't have time
to explain.
Powered by blists - more mailing lists