From: Mark Rutland <mark.rutland@arm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: devicetree <devicetree@vger.kernel.org>,
"Pantelis Antoniou" <pantelis.antoniou@konsulko.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Jailhouse <jailhouse-dev@googlegroups.com>,
"Måns Rullgård" <mans@denx.de>,
"Antonios Motakis" <antonios.motakis@huawei.com>
Subject: Re: Using DT overlays for adding virtual hardware
Date: Wed, 8 Jun 2016 16:17:46 +0100 [thread overview]
Message-ID: <20160608151745.GB13355@leverpostej> (raw)
In-Reply-To: <575828C0.5000008@siemens.com>
On Wed, Jun 08, 2016 at 04:16:32PM +0200, Jan Kiszka wrote:
> Hi all,
>
> already started the discussion off-list with Pantelis, but it's better
> done in public:
>
> I'm currently exploring ways to make Linux recognize dynamically added
> virtual hardware when running under the Jailhouse hypervisor [1]. We
> need to load drivers for inter-partition communication devices that only
> appear after Jailhouse started (which is done from within Linux, i.e.
> long after boot) or when a partition was added later on. Probably, we
> will simply add a virtual PCI host bridge on systems without physical
> PCI and let the IPC device be explored that way (already works on x86).
> Still, that leaves us with hotplug and unplug on hypervisor activation
> and deactivation.
If I've understood correctly you want to use overlays to inject the
virtual PCI host bridge?
Given that you know precisely what you want to inject, I'm not sure I
see the value of using an overlay.
Is there some reason you can't just create a device without having to go
via an intermediate step? As I understand it, Xen does that for (some)
virtual devices provided to Dom0 and DomU.
Thanks,
Mark.
next prev parent reply other threads:[~2016-06-08 15:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 14:16 Using DT overlays for adding virtual hardware Jan Kiszka
2016-06-08 15:17 ` Mark Rutland [this message]
2016-06-08 15:27 ` Jan Kiszka
2016-06-08 15:57 ` Pantelis Antoniou
2016-06-08 16:23 ` Mark Rutland
2016-06-08 16:31 ` Pantelis Antoniou
2016-06-08 16:39 ` Jan Kiszka
2016-06-09 6:03 ` Jan Kiszka
2016-06-21 10:13 ` Jan Kiszka
2016-06-21 10:24 ` Pantelis Antoniou
2016-06-21 11:22 ` Jan Kiszka
2016-06-21 11:35 ` Pantelis Antoniou
2016-06-21 11:43 ` Jan Kiszka
2016-06-21 11:45 ` Pantelis Antoniou
2016-06-21 11:59 ` Jan Kiszka
2016-06-21 13:12 ` Jan Kiszka
2016-06-21 13:29 ` Pantelis Antoniou
2016-06-09 7:22 ` Arnd Bergmann
2016-06-10 14:57 ` Jan Kiszka
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=20160608151745.GB13355@leverpostej \
--to=mark.rutland@arm.com \
--cc=antonios.motakis@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@denx.de \
--cc=pantelis.antoniou@konsulko.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 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).