From: Christoffer Dall <christoffer.dall@linaro.org>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Steve Capper <Steve.Capper@arm.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen Devel <xen-devel@lists.xen.org>,
Bhupinder Thakur <bhupinder.thakur@linaro.org>
Subject: Re: Xen ARM - Exposing a PL011 to the guest
Date: Wed, 30 Nov 2016 17:24:00 +0100 [thread overview]
Message-ID: <20161130162400.GC6647@cbox> (raw)
In-Reply-To: <86800697-5057-3f14-c19f-151e81315133@arm.com>
On Wed, Nov 30, 2016 at 03:29:32PM +0000, Julien Grall wrote:
> Hi all,
>
> Few months ago, Linaro has published the version 2 of the VM
> specification [1].
>
> For those who don't know, the specification provides guidelines to
> guarantee a compliant OS images could run on various hypervisor (e.g
> Xen, KVM).
>
> Looking at the specification, it will require Xen to expose new
> devices to the guest: pl011, rtc, persistent flash (for UEFI
> variables).
>
> The RTC and persistent will only be used by the UEFI firwmare.
Why would a guest booting without UEFI not want to use the RTC directly?
Linux does this on KVM today...
-Christoffer
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-30 16:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:29 Xen ARM - Exposing a PL011 to the guest Julien Grall
2016-11-30 16:24 ` Christoffer Dall [this message]
2016-12-01 15:51 ` Julien Grall
2016-11-30 17:02 ` Volodymyr Babchuk
2016-11-30 22:26 ` Stefano Stabellini
2016-12-01 10:26 ` Christoffer Dall
2016-12-01 21:55 ` Stefano Stabellini
2016-12-16 10:06 ` Bhupinder Thakur
2016-12-16 17:03 ` Julien Grall
2016-12-19 12:20 ` Christoffer Dall
2016-12-19 20:24 ` Stefano Stabellini
2016-12-20 9:46 ` Bhupinder Thakur
2016-12-20 22:29 ` Stefano Stabellini
2016-12-20 12:32 ` Julien Grall
2016-12-20 19:53 ` Stefano Stabellini
2016-12-20 20:26 ` Stefano Stabellini
2016-12-21 19:19 ` Julien Grall
2016-12-21 22:12 ` Stefano Stabellini
2016-12-28 17:49 ` Julien Grall
2016-12-28 17:52 ` Julien Grall
2016-12-29 9:17 ` Bhupinder Thakur
2017-01-03 20:08 ` Stefano Stabellini
2017-01-06 10:18 ` Bhupinder Thakur
2017-01-06 21:54 ` Stefano Stabellini
2017-01-10 11:39 ` Bhupinder Thakur
2017-01-11 0:22 ` Stefano Stabellini
2017-01-17 14:01 ` Julien Grall
2017-01-17 13:31 ` Julien Grall
2017-01-17 19:27 ` Stefano Stabellini
2017-01-27 12:14 ` Bhupinder Thakur
2017-01-27 19:13 ` Stefano Stabellini
2017-01-29 11:06 ` Christoffer Dall
2017-02-03 13:53 ` Bhupinder Thakur
2017-02-03 14:08 ` Julien Grall
2017-02-08 12:39 ` Bhupinder Thakur
2017-02-09 0:10 ` Stefano Stabellini
2017-02-13 8:50 ` Bhupinder Thakur
2017-02-13 21:44 ` Stefano Stabellini
2017-02-15 8:15 ` Bhupinder Thakur
2017-02-15 8:24 ` Bhupinder Thakur
2017-02-15 21:21 ` Stefano Stabellini
2017-02-23 13:15 ` Bhupinder Thakur
2017-02-23 15:00 ` Wei Liu
2017-02-03 14:15 ` Christoffer Dall
2017-01-03 19:38 ` Stefano Stabellini
2016-12-20 12:47 ` Christoffer Dall
2016-12-20 21:33 ` Stefano Stabellini
2016-12-21 11:55 ` Christoffer Dall
2016-12-21 20:32 ` 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=20161130162400.GC6647@cbox \
--to=christoffer.dall@linaro.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Steve.Capper@arm.com \
--cc=bhupinder.thakur@linaro.org \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--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).