From: Anthony PERARD <anthony.perard@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Kevin Stange <kevin@steadfast.net>,
xen-devel@lists.xenproject.org,
George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: PCI Device Subtree Change from Traditional to Upstream
Date: Thu, 25 Jan 2018 18:04:39 +0000 [thread overview]
Message-ID: <20180125180439.GC2183@perard.uk.xensource.com> (raw)
In-Reply-To: <10c96acc-9bb5-713b-93c9-60f06c84bfd5@citrix.com>
On Thu, Jan 25, 2018 at 05:54:36PM +0000, George Dunlap wrote:
> On 01/04/2018 12:52 PM, Anthony PERARD wrote:
> > From: Anthony PERARD <anthony.perard@citrix.com>
> > Subject: [PATCH] libxl_dm: Explicitly put xen-platform device on PCI slot 3
> >
> > In order to do that, we don't use xenfv machine anymore and explicity
> > add the platform device on the command line.
> >
> > Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
>
> Anthony,
>
> It seems like we might want to add the ability to specify which slot we
> want the xen-platform device to occupy. Is it worth thinking of the best
> way to add a patch like this upstream?
I think that would be nice for people who switch from qemu-trad to
QEMU. The only question that remain is, how to name the xl config
option? The rest is to simply take my libxl patch and make it use
the new config option.
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-01-25 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 17:40 PCI Device Subtree Change from Traditional to Upstream Kevin Stange
2017-12-20 17:44 ` George Dunlap
2018-01-03 17:57 ` Anthony PERARD
2018-01-03 23:10 ` Kevin Stange
2018-01-04 12:52 ` Anthony PERARD
2018-01-04 13:26 ` Paul Durrant
2018-01-04 21:17 ` Kevin Stange
2018-01-05 9:03 ` Paul Durrant
2018-01-05 17:05 ` Kevin Stange
2018-01-04 21:16 ` Kevin Stange
2018-01-05 17:10 ` Kevin Stange
2018-01-05 20:56 ` Kevin Stange
2018-01-25 17:54 ` George Dunlap
2018-01-25 18:04 ` Anthony PERARD [this message]
2018-01-25 18:14 ` George Dunlap
2018-01-26 10:38 ` Paul Durrant
2019-04-08 9:46 ` George Dunlap
2019-04-08 9:46 ` [Xen-devel] " George Dunlap
2019-04-08 9:51 ` Paul Durrant
2019-04-08 9:51 ` [Xen-devel] " Paul Durrant
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=20180125180439.GC2183@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--cc=kevin@steadfast.net \
--cc=xen-devel@lists.xenproject.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 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.