From: Greg Law <glaw@solarflare.com>
To: Masroor Vettuparambil <Masroor.Vettuparambil@neterion.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen support for PCI-SIG I/O Virtualization
Date: Wed, 16 Jan 2008 17:55:43 +0000 [thread overview]
Message-ID: <478E451F.5080105@solarflare.com> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7702D4F76C@nekter>
Masroor Vettuparambil wrote:
> Hi,
>
> what is the current support of Xen for PCI-SIG IOV SR/MR spec?
> I have a PCIe device which supports multiple virtual functions(VF), and
> want to enable direct assignment of each of these VFs to different domUs.
> So is it possible to assign a PCIe virtual channel/function to domU
> directly?
Have you seen the work we did recently to allow smart NIC's to be
accessed directly from the guest? Essentially your "accelerated" driver
is a plugin to netfront (which knows how to send/receive packets with
safe direct access hardware to the NIC), and a plugin for netback which
deals with the privileged part of programming the NIC (e.g. creating
virtual devices and handing them out to the guests as appropriate).
Among other things, this architecture means you can support migrating to
machines with no smart hardware, or a different smart NIC.
Let me know if you want to know more.
As far as programming the IOMMU goes, I've seen various patches flying
around so I know work has been done here, but I don't know any more than
that.
Cheers,
Greg
--
Greg Law +44 1223 518 040
next prev parent reply other threads:[~2008-01-16 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 8:39 Xen support for PCI-SIG I/O Virtualization Masroor Vettuparambil
2008-01-16 17:55 ` Greg Law [this message]
2008-01-17 0:20 ` Woller, Thomas
2008-01-17 11:28 ` Greg Law
2008-01-17 12:02 ` Masroor Vettuparambil
2008-01-18 17:31 ` Greg Law
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=478E451F.5080105@solarflare.com \
--to=glaw@solarflare.com \
--cc=Masroor.Vettuparambil@neterion.com \
--cc=xen-devel@lists.xensource.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.