From: Eric Auger <eric.auger@linaro.org>
To: Yehuda Yitschak <yehuday@marvell.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Shadi Ammouri <shadi@marvell.com>, Yuval Caduri <cyuval@marvell.com>
Subject: Re: [Qemu-devel] Assigning an eth port to a guest VM
Date: Mon, 15 Jun 2015 15:42:02 +0200 [thread overview]
Message-ID: <557ED62A.8050409@linaro.org> (raw)
In-Reply-To: <f62ae47c39774443bb23f4090b1f791d@IL-EXCH02.marvell.com>
Hi Yehuda,
On 06/15/2015 01:01 PM, Yehuda Yitschak wrote:
> 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
>>
>> Hello
>>
>> I would to ask your advice on how to assign a semi-virtualized Ethernet port
>> to a guest VM
>>
>> The eth port's HW partially supports virtualization since the data path MMIO
>> 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.
>>
>> 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 ?
Yes to me you're correct.
>>
>> Are there any standard methods for achieving this ?
>> Is there an example for such an existing HW in QEMU ?
Not yet unfortunately. To my knowledge the only platform devices that
were assigned with QEMU VFIO platform were standalone duplicated
devices, PL330, Calxeda Xgmac, SATA. So you are a trailblazer on that
track.
Best Regards
Eric
>>
>> Thanks
>>
>> Yehuda Yitschak
next prev parent reply other threads:[~2015-06-15 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 11:01 [Qemu-devel] Assigning an eth port to a guest VM Yehuda Yitschak
2015-06-15 13:42 ` Eric Auger [this message]
2015-06-15 16:52 ` Yehuda Yitschak
2015-06-15 16:59 ` Eric Auger
2015-06-15 17:15 ` Alex Williamson
2015-06-15 17:45 ` Yehuda Yitschak
2015-06-15 17:55 ` Eric Auger
2015-06-15 18:31 ` Alex Williamson
2015-06-16 11:21 ` Yehuda Yitschak
2015-06-16 14:43 ` Alex Williamson
2015-06-17 17:16 ` Yehuda Yitschak
-- strict thread matches above, loose matches on Subject: below --
2015-06-15 6:35 Yehuda Yitschak
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=557ED62A.8050409@linaro.org \
--to=eric.auger@linaro.org \
--cc=cyuval@marvell.com \
--cc=qemu-devel@nongnu.org \
--cc=shadi@marvell.com \
--cc=yehuday@marvell.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).