From: George Dunlap <George.Dunlap@citrix.com>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Stefano Stabellini <stefano.stabellini@xilinx.com>,
Julien Grall <jgrall@amazon.com>,
"Julien Grall" <Julien.grall.oss@gmail.com>,
Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
Jan Beulich <jbeulich@suse.com>, Rich Persaud <persaur@gmail.com>,
Bertrand Marquis <Bertrand.Marquis@arm.com>,
"luca.fancellu@arm.com" <luca.fancellu@arm.com>,
Paul Durrant <paul@xen.org>,
Adam Schwalm <adam.schwalm@starlab.io>
Subject: Re: [PATCH 1/2] docs/designs/launch: hyperlaunch design document
Date: Wed, 24 Mar 2021 13:15:48 +0000 [thread overview]
Message-ID: <532A93C8-81F9-4254-A9B6-B6E3462923A9@citrix.com> (raw)
In-Reply-To: <CACMJ4GZMNfbCjTKR5ngQBMwwAfUnSOptP+UJV8BcNqKAUy9Row@mail.gmail.com>
> On Mar 24, 2021, at 12:53 PM, Christopher Clark <christopher.w.clark@gmail.com> wrote:
>
> Do you know if there is a need to perform work to support the
> assignment of PCI devices at the point of domain creation (ie. in
> domain_create), rather than handling it in a later step of domain
> configuration, prior to the domain being started?
AIUI, libxl actually does the latter: That is, PCI devices are added to the domain after the domain and qemu have been set up, but before they have been unpaused. One advantage of this is that it’s the same codepath for adding PCI devices at domain creation as for hotplug.
-George
next prev parent reply other threads:[~2021-03-24 13:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 3:18 [PATCH 0/2] Introducing hyperlaunch capability design (formerly: DomB mode of dom0less) Daniel P. Smith
2021-03-16 3:18 ` [PATCH 1/2] docs/designs/launch: hyperlaunch design document Daniel P. Smith
2021-03-18 16:43 ` Roger Pau Monné
2021-03-23 17:39 ` Christopher Clark
2021-03-24 8:01 ` Roger Pau Monné
2021-03-24 12:53 ` Christopher Clark
2021-03-24 13:15 ` George Dunlap [this message]
2021-03-24 19:10 ` Stefano Stabellini
2021-03-25 8:07 ` Jan Beulich
2021-03-25 8:32 ` Roger Pau Monné
2021-03-25 9:14 ` George Dunlap
2021-03-25 9:49 ` Roger Pau Monné
2021-03-25 16:55 ` Stefano Stabellini
2021-04-07 20:14 ` Christopher Clark
2021-03-16 3:18 ` [PATCH] docs/designs/launch: hyperlaunch device tree Daniel P. Smith
2021-03-16 3:56 ` [PATCH 0/2] Introducing hyperlaunch capability design (formerly: DomB mode of dom0less) Daniel P. Smith
2021-03-30 14:31 ` Jan Beulich
2021-04-07 19:23 ` Christopher Clark
2021-04-08 5:56 ` Jan Beulich
2021-04-15 22:33 ` Christopher Clark
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=532A93C8-81F9-4254-A9B6-B6E3462923A9@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Julien.grall.oss@gmail.com \
--cc=adam.schwalm@starlab.io \
--cc=christopher.w.clark@gmail.com \
--cc=dpsmith@apertussolutions.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=luca.fancellu@arm.com \
--cc=paul@xen.org \
--cc=persaur@gmail.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@xilinx.com \
--cc=wl@xen.org \
--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 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).