Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640826 > unrolled thread
| Started by | PGNet Dev <pgnet.dev@gmail.com> |
|---|---|
| First post | 2017-05-13 04:40 +0200 |
| Last post | 2017-05-13 22:00 +0200 |
| Articles | 3 on this page of 23 — 7 participants |
Back to article view | Back to linux.kernel
HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 04:40 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-13 19:50 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 20:30 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-13 21:30 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 21:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:00 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 22:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 23:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Juergen Gross <jgross@suse.com> - 2017-05-14 19:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-13 22:30 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 23:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-13 23:40 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-14 00:00 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-14 00:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-14 01:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-14 17:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-14 19:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2017-05-15 20:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-17 02:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:10 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 22:00 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Clemens Ladisch <clemens@ladisch.de> - 2017-05-13 22:00 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Andrew Cooper <andrew.cooper3@citrix.com> |
|---|---|
| Date | 2017-05-13 22:10 +0200 |
| Subject | Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? |
| Message-ID | <tGLd8-82A-9@gated-at.bofh.it> |
| In reply to | #1640984 |
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
[toc] | [prev] | [next] | [standalone]
| From | PGNet Dev <pgnet.dev@gmail.com> |
|---|---|
| Date | 2017-05-13 22:00 +0200 |
| Message-ID | <tGLmN-88a-1@gated-at.bofh.it> |
| In reply to | #1640971 |
On 5/13/17 12:45 PM, Clemens Ladisch wrote: > That table is not used by hpet_acpi_add; you have to check for the device > that mentions "PNP0103" in the DSDT table. > > But anyway, as far as I can tell from my own machine, the _CRS in the > DSDT table never lists the HPET interrupts, and the HPET registration is > always done by hpet_reserve_platform_timers() in arch/x86/kernel/hpet.c. > Try adding logging to hpet_late_init() to find out why it aborts. I assume you mean in kernel source code? I'm using distro packages for both kernel & Xen -- not DIY building.
[toc] | [prev] | [next] | [standalone]
| From | Clemens Ladisch <clemens@ladisch.de> |
|---|---|
| Date | 2017-05-13 22:00 +0200 |
| Message-ID | <tGLmN-88a-3@gated-at.bofh.it> |
| In reply to | #1640971 |
Randy Dunlap wrote: > On 05/12/17 19:30, PGNet Dev wrote: >> dmesg | grep -i hpet >> [ 8.491738] hpet_acpi_add: no address or irqs in _CRS > > Above line marks a big failure. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> Disassembling the firmware acpi tables >> >> cat /sys/firmware/acpi/tables/HPET > /var/tmp/hpet.out >> iasl -d /var/tmp/hpet.out That table is not used by hpet_acpi_add; you have to check for the device that mentions "PNP0103" in the DSDT table. But anyway, as far as I can tell from my own machine, the _CRS in the DSDT table never lists the HPET interrupts, and the HPET registration is always done by hpet_reserve_platform_timers() in arch/x86/kernel/hpet.c. Try adding logging to hpet_late_init() to find out why it aborts. Regards, Clemens
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.kernel
csiph-web