From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758070AbdEMUQX (ORCPT ); Sat, 13 May 2017 16:16:23 -0400 Received: from ppsw-30.csi.cam.ac.uk ([131.111.8.130]:60529 "EHLO ppsw-30.csi.cam.ac.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751131AbdEMUQW (ORCPT ); Sat, 13 May 2017 16:16:22 -0400 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? To: pgnet.dev@gmail.com, Randy Dunlap , "linux-kernel@vger.kernel.org" , Clemens Ladisch , xen-devel@lists.xenproject.org, Juergen Gross References: <61d510e2-0353-ddf2-f63c-8a1688a6b6ed@gmail.com> <9ff8ca5a-727d-13c3-7c39-6383e00d2edf@infradead.org> <2c84903a-ab24-a073-378b-82fe6052e6ac@infradead.org> <927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com> <34c505d9-9dc6-8982-4875-74dedfc5e0d1@gmail.com> From: Andrew Cooper Cc: Jan Beulich Message-ID: <350fb783-80b5-669f-7015-46c45226ed67@citrix.com> Date: Sat, 13 May 2017 21:16:17 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-GB Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/05/2017 21:05, PGNet Dev wrote: > On 5/13/17 12:59 PM, Andrew Cooper wrote: >> Ok. Lack of a clocksource is to be expected. >> >> The reason why the HPETs are unavailable is that dom0 is not a position >> to program them; dom0 doesn't know what Xen has set up in the IDT. >> >> Use `xl dmesg` to get to the hypervisor dmesg log. You should see >> mention of the HPET in there if Xen has found it. > > back to the error at hand ... > > xl dmesg | grep -i hpet > [ 1.365876] hpet_acpi_add: no address or irqs in _CRS > [ 1.365876] hpet_acpi_add: no address or irqs in _CRS > > again, only present when booting with Xen. > > same kernel, no Xen, no such error. We don't have code like that in upstream Xen. No function with that name, or a string which looks like that error message. http://marc.info/?l=linux-kernel&m=149464267427111&w=2 indicates that you are using a SuSE hypervisor. Jan/Juergen: Any ideas? This looks as if it is something local to your patch queue. ~Andrew