All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yehuda Yitschak <yehuday@marvell.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Shadi Ammouri <shadi@marvell.com>, Yuval Caduri <cyuval@marvell.com>
Subject: [Qemu-devel] Assigning an eth port to a guest VM
Date: Mon, 15 Jun 2015 06:35:19 +0000	[thread overview]
Message-ID: <004767f849d1410ba2450c63ec4e6166@IL-EXCH02.marvell.com> (raw)

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 ?

Are there any standard methods for achieving this ?
Is there an example for such an existing HW in QEMU ?

Thanks 

Yehuda Yitschak

             reply	other threads:[~2015-06-15  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  6:35 Yehuda Yitschak [this message]
2015-06-15 11:01 [Qemu-devel] Assigning an eth port to a guest VM Yehuda Yitschak
2015-06-15 13:42 ` Eric Auger
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

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=004767f849d1410ba2450c63ec4e6166@IL-EXCH02.marvell.com \
    --to=yehuday@marvell.com \
    --cc=cyuval@marvell.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shadi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.