From: Knut Omang <knut.omang@oracle.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Tal Attaly <talat@mellanox.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Elijah Shakkour <elijahs@mellanox.com>
Subject: Re: [Qemu-devel] Question: SRIOV support over Win Hyper-V VM running in QEMU process on Linux host
Date: Thu, 26 Jul 2018 19:22:07 +0200 [thread overview]
Message-ID: <1532625727.2458.183.camel@oracle.com> (raw)
In-Reply-To: <20180726201113-mutt-send-email-mst@kernel.org>
On Thu, 2018-07-26 at 20:11 +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 26, 2018 at 10:42:52AM -0600, Alex Williamson wrote:
> > On Thu, 26 Jul 2018 19:14:45 +0300
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >
> > > On Thu, Jul 26, 2018 at 06:51:13PM +0300, Marcel Apfelbaum wrote:
> > > > Hi
> > > >
> > > > On 07/26/2018 05:52 PM, Stefan Hajnoczi wrote:
> > > > > On Thu, Jul 12, 2018 at 07:33:14AM +0000, Elijah Shakkour wrote:
> > > > > > Hey,
> > > > > >
> > > > > > Our team is adding a NIC functional emulation to QEMU.
> > > > > > One of the features we are adding to this NIC is SRIOV.
> > > > > >
> > > > > > Here is the error message I get when checking SRIOV support of our
> > > > > > emulated NIC on Win2016 server (the hyper-v VM).
> > > > > > "
> > > > > > SR-IOV cannot be used on this system as the PCI Express hardware
> > > > > > does not support Access Control Services (ACS) at any root port.
> > > >
> > > > QEMU's emulated PCI Express Root Ports do not support ACS yet, however I
> > > > am
> > > > not sure ACS is a prerequisite
> > > > for SR-IOV.
> >
> > ACS is certainly not a prerequisite for SR-IOV.
> >
> > > Looks like windows blocks dev assignment in nested VMs without it.
> > > Thinking about it, doesn't vfio do the same by default? I think vfio has
> > > a flag to override this though.
> >
> > IOMMU grouping in Linux takes isolation via ACS and device specific
> > mechanisms into account, limiting the granularity with which a
> > userspace driver can claim ownership of devices,
>
> In that you must assign all devices behind this port as a group?
Yes, that's why I needed to add PCIe config space ACS support in ioh3420:
to be able to use VFIO to pass through individual VFs to different L2 VMs with
"plain" kernels on the L1 host which owns the SR/IOV device.
Knut
> > but it doesn't
> > actually prevent enabling SR-IOV on the endpoint. It just makes it
> > less useful if your intention is to use SR-IOV for device assignment.
> > The only overrides for this are out-of-tree. Thanks,
> >
> >
> > Alex
>
>
next prev parent reply other threads:[~2018-07-26 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB5PR05MB11605C65D7D734C9354F0421D54F0@DB5PR05MB1160.eurprd05.prod.outlook.com>
[not found] ` <1407239306.11199051.1530240887935.JavaMail.zimbra@redhat.com>
[not found] ` <20180705194311-mutt-send-email-mst@kernel.org>
[not found] ` <DB5PR05MB1160D84E747DA480435B6605D5440@DB5PR05MB1160.eurprd05.prod.outlook.com>
[not found] ` <DB5PR05MB1160BB381473C723C8336EC2D55A0@DB5PR05MB1160.eurprd05.prod.outlook.com>
[not found] ` <AM5PR0501MB2499CB4F2D01BCDA47C0ACB6C95A0@AM5PR0501MB2499.eurprd05.prod.outlook.com>
2018-07-12 7:33 ` [Qemu-devel] Question: SRIOV support over Win Hyper-V VM running in QEMU process on Linux host Elijah Shakkour
2018-07-26 14:52 ` Stefan Hajnoczi
2018-07-26 15:51 ` Marcel Apfelbaum
2018-07-26 16:14 ` Michael S. Tsirkin
2018-07-26 16:34 ` Marcel Apfelbaum
2018-07-26 16:38 ` Michael S. Tsirkin
2018-07-26 16:42 ` Alex Williamson
2018-07-26 17:11 ` Michael S. Tsirkin
2018-07-26 17:22 ` Knut Omang [this message]
2018-07-26 17:22 ` Alex Williamson
2018-07-26 16:38 ` Knut Omang
2018-07-26 16:41 ` Michael S. Tsirkin
2018-07-26 16:42 ` Knut Omang
2018-07-26 17:05 ` Marcel Apfelbaum
2018-07-26 17:25 ` Knut Omang
2018-07-26 17:27 ` Knut Omang
2018-07-26 17:28 ` Michael S. Tsirkin
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=1532625727.2458.183.camel@oracle.com \
--to=knut.omang@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=elijahs@mellanox.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=talat@mellanox.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.