From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Artem Mygaiev <artem_mygaiev@epam.com>
Cc: "Edgar Iglesias (edgar.iglesias@xilinx.com)"
<edgar.iglesias@xilinx.com>, Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
casionwoo <casionwoo@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: Xen ARM small task (WAS: Re: [Xen Question])
Date: Wed, 23 Nov 2016 17:38:27 +0100 [thread overview]
Message-ID: <20161123163827.GX9606@toto> (raw)
In-Reply-To: <addefcbf-5949-8452-1e19-ddcedca83b35@epam.com>
On Wed, Nov 23, 2016 at 06:26:06PM +0200, Artem Mygaiev wrote:
> On 23.11.16 17:19, Julien Grall wrote:
> > There is a couple of usecase where we cannot use PV console:
> > - Running unmodified baremetal application as guest. Those
> > applications will not have PV driver.
> Well, I somehow missed that requirement is to run *unmodified*
> applications... I think it will be pretty hard to provide all the HW
> infrastructure expected and UARTs as I know them have all possible
> issues & workarounds.
Hi Artem,
The way I see this is not for Xen to provide support for any HW for any
platform on all platforms.
The way I see it is that on a given platform, for example the ZynqMP.
You can run Xen as a partitioning Hypervisor essentially using device
passthrough to assign various real HW devices to each VM.
The various guests can run unmodified because they each see a subset
of the platform.
It is useful to have vuarts that go are shared into a single one.
Cheers,
Edgar
> > - Guest compliant with the VM system specification for ARM [1]. A
> > pl011 is required.
> Yes, indeed, a subset of PL011 registers is required, unfortunately I
> was not familiar with that spec, thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-23 16:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMguKxbBxZ_0Za8dAUVUbz1hPT5+QfTsycZCftpi99YsJZ0+Vg@mail.gmail.com>
[not found] ` <36d47cc0-839b-bd4d-fd73-334435e2dca1@arm.com>
2016-11-10 12:13 ` [Xen Question] casionwoo
2016-11-10 12:24 ` Xen ARM small task (WAS: Re: [Xen Question]) Julien Grall
2016-11-11 2:24 ` Stefano Stabellini
2016-11-11 9:46 ` Julien Grall
2016-11-11 16:59 ` Edgar E. Iglesias
2016-11-14 4:07 ` 유정우
2016-11-11 19:55 ` Stefano Stabellini
2016-11-14 20:12 ` Julien Grall
2016-11-17 17:26 ` Stefano Stabellini
2016-11-17 17:57 ` Julien Grall
2016-11-18 18:58 ` Stefano Stabellini
2016-11-21 19:50 ` Edgar E. Iglesias
2016-11-21 21:01 ` Stefano Stabellini
2016-11-21 21:13 ` Edgar E. Iglesias
2016-11-21 21:24 ` Julien Grall
2016-11-21 21:57 ` Edgar E. Iglesias
2016-11-22 19:06 ` Stefano Stabellini
2016-11-22 19:36 ` Julien Grall
2016-11-23 15:10 ` Artem Mygaiev
2016-11-23 15:19 ` Julien Grall
2016-11-23 16:26 ` Artem Mygaiev
2016-11-23 16:38 ` Edgar E. Iglesias [this message]
2016-11-23 18:32 ` Julien Grall
2016-11-24 13:29 ` Edgar E. Iglesias
2016-11-23 19:55 ` Stefano Stabellini
2016-11-25 16:52 ` Julien Grall
2016-12-01 2:07 ` Stefano Stabellini
2016-12-01 15:47 ` Julien Grall
2016-12-01 21:33 ` Stefano Stabellini
2016-12-05 14:13 ` Julien Grall
2016-12-05 20:25 ` Stefano Stabellini
2016-12-06 16:05 ` Julien Grall
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=20161123163827.GX9606@toto \
--to=edgar.iglesias@gmail.com \
--cc=artem_mygaiev@epam.com \
--cc=casionwoo@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.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 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.