From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52758)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <yehuday@marvell.com>) id 1Z4S9a-0000AN-4z
	for qemu-devel@nongnu.org; Mon, 15 Jun 2015 07:02:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <yehuday@marvell.com>) id 1Z4S9V-0000mu-Qb
	for qemu-devel@nongnu.org; Mon, 15 Jun 2015 07:02:10 -0400
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]:25107)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <yehuday@marvell.com>) id 1Z4S9V-0000lS-GU
	for qemu-devel@nongnu.org; Mon, 15 Jun 2015 07:02:05 -0400
From: Yehuda Yitschak <yehuday@marvell.com>
Date: Mon, 15 Jun 2015 11:01:54 +0000
Message-ID: <f62ae47c39774443bb23f4090b1f791d@IL-EXCH02.marvell.com>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Assigning an eth port to a guest VM
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Shadi Ammouri <shadi@marvell.com>, Yuval Caduri <cyuval@marvell.com>, "eric.auger@linaro.org" <eric.auger@linaro.org>

Cc: Eric Auger

> -----Original Message-----
> From: Yehuda Yitschak
> Sent: Monday, June 15, 2015 9:35
> To: qemu-devel@nongnu.org
> Cc: Yuval Caduri; Shadi Ammouri
> Subject: Assigning an eth port to a guest VM
>=20
> Hello
>=20
> I would to ask your advice on how to assign a semi-virtualized Ethernet p=
ort
> to a guest VM
>=20
> The eth port's HW partially supports virtualization since the data path M=
MIO
> registers (which controls rx/tx operation) are duplicated per VM.
> So for the run-time operation the guest can directly access the MMIO
> registers, using VFIO-PLATFORM, and enjoy the performance benefit.
>=20
> However for the initial setup and occasional configuration the guest need=
 to
> access control path registers which are shared for all guests.
> AFAIK this is usually done with HW emulation using trap & emulate with
> QEMU.
> So, to the best of my knowledge I need a mix of VFIO and HW emulation to
> get the port to work with device assignment , right ?
>=20
> Are there any standard methods for achieving this ?
> Is there an example for such an existing HW in QEMU ?
>=20
> Thanks
>=20
> Yehuda Yitschak