From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Randy Dunlap <rdunlap@infradead.org>,
pgnet.dev@gmail.com,
"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 20:38:33 +0100 [thread overview]
Message-ID: <927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com> (raw)
In-Reply-To: <2c84903a-ab24-a073-378b-82fe6052e6ac@infradead.org>
On 13/05/2017 20:28, Randy Dunlap wrote:
> On 05/13/17 11:26, PGNet Dev wrote:
>> On 5/13/17 10:41 AM, Randy Dunlap wrote:
>>> [adding HPET driver maintainer]
>> Thanks
>>
>>> A couple of comments below...
>>>> In BIOS, HPET's enabled.
>>> How about if you just boot Linux without Xen? Does HPET show up then?
>> yes, it appears so:
>>
>> cat devices/system/clocksource/clocksource0/available
>> tsc hpet acpi_pm
> Adding xen mailing list:
>
> Is HPET support a known issue in Xen?
What is the issue here?
Xen owns (and may use) any HPETs in the system. They are purposefully
unavailable to even dom0.
~Andrew
next prev parent reply other threads:[~2017-05-13 20:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 2:30 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 ` Andrew Cooper [this message]
2017-05-13 19:49 ` [Xen-devel] " PGNet Dev
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:16 ` Andrew Cooper
2017-05-13 21:07 ` PGNet Dev
2017-05-14 17:13 ` Juergen Gross
2017-05-13 20:28 ` Valentin Vidic
2017-05-13 21:06 ` PGNet Dev
2017-05-13 21:32 ` Valentin Vidic
2017-05-13 21:58 ` 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 17:41 ` Randy Dunlap
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:15 ` PGNet Dev
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=927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pgnet.dev@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®