From: PGNet Dev <pgnet.dev@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?
Date: Sat, 13 May 2017 12:49:32 -0700 [thread overview]
Message-ID: <34c505d9-9dc6-8982-4875-74dedfc5e0d1@gmail.com> (raw)
In-Reply-To: <927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com>
On 5/13/17 12:38 PM, Andrew Cooper wrote:
> What is the issue here?
>
> Xen owns (and may use) any HPETs in the system. They are purposefully
> unavailable to even dom0.
The issue is that, when booting to Xen, hpet is not advertised as an available clocksource, AND reports the hpet boot error pointed out by Randy.
Following
https://wiki.xen.org/wiki/Xen_power_management#HPET_as_broadcast_timer_source_.28clocksource.29_.3D
there's discussion there re: 'if HPET is available / not missing'.
It appears to be available only booting to non-Xen.
What specific indication does one look for that Xen's using available hpet?
next prev parent reply other threads:[~2017-05-13 19:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 2:30 HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev
2017-05-13 17:41 ` Randy Dunlap
2017-05-13 18:26 ` PGNet Dev
2017-05-13 19:28 ` Randy Dunlap
2017-05-13 19:38 ` [Xen-devel] " Andrew Cooper
2017-05-13 19:38 ` Andrew Cooper
2017-05-13 19:49 ` PGNet Dev [this message]
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 19:59 ` [Xen-devel] " Andrew Cooper
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:16 ` [Xen-devel] " Andrew Cooper
2017-05-13 21:07 ` PGNet Dev
2017-05-13 21:07 ` PGNet Dev
2017-05-14 17:13 ` [Xen-devel] " Juergen Gross
2017-05-14 17:13 ` Juergen Gross
2017-05-13 20:16 ` Andrew Cooper
2017-05-13 20:28 ` Valentin Vidic
2017-05-13 20:28 ` [Xen-devel] " Valentin Vidic
2017-05-13 21:06 ` PGNet Dev
2017-05-13 21:32 ` Valentin Vidic
2017-05-13 21:32 ` [Xen-devel] " Valentin Vidic
2017-05-13 21:58 ` PGNet Dev
2017-05-13 21:58 ` [Xen-devel] " PGNet Dev
2017-05-13 22:15 ` Valentin Vidic
2017-05-13 23:17 ` PGNet Dev
2017-05-14 15:39 ` Andrew Cooper
2017-05-14 15:39 ` [Xen-devel] " Andrew Cooper
2017-05-14 17:41 ` Randy Dunlap
2017-05-14 17:41 ` [Xen-devel] " Randy Dunlap
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:15 ` PGNet Dev
2017-05-17 0:15 ` [Xen-devel] " PGNet Dev
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-13 23:17 ` PGNet Dev
2017-05-13 22:15 ` Valentin Vidic
2017-05-13 21:06 ` PGNet Dev
2017-05-13 19:49 ` PGNet Dev
2017-05-13 19:28 ` Randy Dunlap
2017-05-13 19:45 ` Clemens Ladisch
2017-05-13 19:52 ` PGNet Dev
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=34c505d9-9dc6-8982-4875-74dedfc5e0d1@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 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.