From: PGNet Dev <pgnet.dev@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?
Date: Sat, 13 May 2017 11:26:31 -0700 [thread overview]
Message-ID: <ccad7dbf-2136-ea7e-1919-8d94460096c9@gmail.com> (raw)
In-Reply-To: <9ff8ca5a-727d-13c3-7c39-6383e00d2edf@infradead.org>
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
>> [ 8.491738] hpet_acpi_add: no address or irqs in _CRS
>
> Above line marks a big failure. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I suspected that's problematic.
In the non-Xen case
dmesg | grep -i hpet
[ 0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM
SMCI--MB 01072009 AMI. 00000005)
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 133484882848 ns
[ 0.000000] hpet clockevent registered
[ 0.144010] DMAR-IR: HPET id 0 under DRHD base 0xfed90000
[ 1.398047] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 1.404226] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 1.412080] clocksource: Switched to clocksource hpet
[ 3.627234] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes
nvram, hpet irqs
next prev parent reply other threads:[~2017-05-13 18:26 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 [this message]
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 ` [Xen-devel] " PGNet Dev
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:16 ` Andrew Cooper
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 ` Juergen Gross
2017-05-14 17:13 ` [Xen-devel] " Juergen Gross
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:06 ` [Xen-devel] " PGNet Dev
2017-05-13 21:32 ` 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 22:15 ` [Xen-devel] " Valentin Vidic
2017-05-13 23:17 ` PGNet Dev
2017-05-13 23:17 ` [Xen-devel] " PGNet Dev
2017-05-14 15:39 ` Andrew Cooper
2017-05-14 17:41 ` Randy Dunlap
2017-05-14 17:41 ` Randy Dunlap
2017-05-14 15:39 ` Andrew Cooper
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-15 18:06 ` [Xen-devel] " Austin S. Hemmelgarn
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:15 ` [Xen-devel] " PGNet Dev
2017-05-17 0:15 ` PGNet Dev
2017-05-13 21:32 ` Valentin Vidic
2017-05-13 19:59 ` Andrew Cooper
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=ccad7dbf-2136-ea7e-1919-8d94460096c9@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.