From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
HW42 <hw42@ipsumj.de>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: PCI passthrough with stubdomain
Date: Fri, 23 Sep 2016 11:35:27 -0400 [thread overview]
Message-ID: <20160923153527.GB25028@char.us.oracle.com> (raw)
In-Reply-To: <20160923142541.GB31510@mail-itl>
On Fri, Sep 23, 2016 at 04:25:41PM +0200, Marek Marczykowski-Górecki wrote:
> On Fri, Sep 23, 2016 at 03:27:07PM +0200, Samuel Thibault wrote:
> > Marek Marczykowski-Górecki, on Fri 23 Sep 2016 10:48:14 +0200, wrote:
> > > I'm still trying to get PCI passthrough working with stubdomain and
> > > without qemu in dom0 (even for just vfb/vkbd backends). How is this
> > > supposed to work?
> >
> > Just as I recall from my memory:
> >
> > > 1. Should xen-pcifront in the target domain be used (and consequently,
> > > should xen-pciback be set for it)?
> >
> > I guess that could work.
>
> Could, or should? ;)
>
> In the meantime, I've found this in xen-pcifront driver:
>
> static int __init pcifront_init(void)
> {
> if (!xen_pv_domain() || xen_initial_domain())
> return -ENODEV;
>
> So, it looks like pcifront is not used in PV domain.
You mean in HVM domains.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-23 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:48 PCI passthrough with stubdomain Marek Marczykowski-Górecki
2016-09-23 9:22 ` Jan Beulich
2016-09-23 13:27 ` Samuel Thibault
2016-09-23 14:25 ` Marek Marczykowski-Górecki
2016-09-23 14:51 ` Samuel Thibault
2016-09-23 18:56 ` Marek Marczykowski-Górecki
2016-09-23 21:00 ` Samuel Thibault
2016-09-23 21:04 ` Marek Marczykowski-Górecki
2016-09-23 15:35 ` Konrad Rzeszutek Wilk [this message]
2016-09-23 18:47 ` Marek Marczykowski-Górecki
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=20160923153527.GB25028@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=hw42@ipsumj.de \
--cc=marmarek@invisiblethingslab.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.org \
/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).