From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759335AbdENPjz (ORCPT ); Sun, 14 May 2017 11:39:55 -0400 Received: from smtp.ctxuk.citrix.com ([185.25.65.24]:61975 "EHLO SMTP.EU.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759314AbdENPjn (ORCPT ); Sun, 14 May 2017 11:39:43 -0400 X-IronPort-AV: E=Sophos;i="5.38,340,1491264000"; d="scan'208";a="46000721" Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? To: , Valentin Vidic References: <2c84903a-ab24-a073-378b-82fe6052e6ac@infradead.org> <927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com> <34c505d9-9dc6-8982-4875-74dedfc5e0d1@gmail.com> <20170513202811.j5mhumhvow3gadms@gavran.carpriv.carnet.hr> <20170513213215.wxkskhyvbu7rz7n7@gavran.carpriv.carnet.hr> <20170513221536.bmijpvmv47pab75c@gavran.carpriv.carnet.hr> <5c0c01ae-775f-55b0-934e-90f81eae8ea3@gmail.com> CC: Randy Dunlap , "linux-kernel@vger.kernel.org" , Clemens Ladisch , From: Andrew Cooper Message-ID: <5dc605c2-6242-17fb-c98a-4de61d31da04@citrix.com> Date: Sun, 14 May 2017 16:39:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <5c0c01ae-775f-55b0-934e-90f81eae8ea3@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To AMSPEX02CL02.citrite.net (10.69.22.126) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/05/17 00:17, PGNet Dev wrote: > On 5/13/17 3:15 PM, Valentin Vidic wrote: >> Try booting without 'hpet=force,verbose clocksource=hpet' and it should >> select xen by default: > Nope. Well, not quite ... > > With both > > 'hpet=force,verbose clocksource=hpet' > > removed, I end up with > > cat /sys/devices/system/clocksource/clocksource0/available_clocksource > tsc xen > cat /sys/devices/system/clocksource/clocksource0/current_clocksource > tsc > > But with > > clocksource=xen > > *explicitly* added > > cat /sys/devices/system/clocksource/clocksource0/available_clocksource > tsc xen > cat /sys/devices/system/clocksource/clocksource0/current_clocksourcexen > xen > > and in *console*, NOT dmesg, output, > > grep -i hpet tmp.txt > (XEN) ACPI: HPET 9E8298F8, 0038 (r1 SUPERM SMCI--MB 1072009 AMI. 5) > (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 > (XEN) [VT-D] MSI HPET: 0000:f0:0f.0 > (XEN) Platform timer is 14.318MHz HPET > [ 0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 000000 > [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 > [ 0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 000000 > [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 > [ 8.515245] hpet_acpi_add: no address or irqs in _CRS > [ 8.515245] hpet_acpi_add: no address or irqs in _CRS > (XEN) [2017-05-13 23:04:27] HVM1 save: HPET > > > > and > > dmesg | grep -i clocksource | grep -v line: > [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns > [ 0.004000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns > [ 0.375709] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns > [ 4.656634] clocksource: Switched to clocksource xen > [ 8.912897] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2c94dffea94, max_idle_ns: 440795361700 ns > > jiffies, now? hm. no idea where that came from. and why the 'tsc' ? > > So I'm still unclear -- is this^ now, correctly "all" using MSI/HPET? What are you trying to achieve? It is still not clear despite all on this thread. The Linux HEPT error messages are non-ideal, but there is no way dom0 will ever be able to use clocksource=hpet when running under Xen. ~Andrew