From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1758404AbdEMUF0 (ORCPT <rfc822;w@1wt.eu>);
        Sat, 13 May 2017 16:05:26 -0400
Received: from mail-pf0-f196.google.com ([209.85.192.196]:35908 "EHLO
        mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754844AbdEMUFZ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 13 May 2017 16:05:25 -0400
Reply-To: pgnet.dev@gmail.com
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?
To: Andrew Cooper <andrew.cooper3@citrix.com>,
        Randy Dunlap <rdunlap@infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Clemens Ladisch <clemens@ladisch.de>, xen-devel@lists.xenproject.org
References: <61d510e2-0353-ddf2-f63c-8a1688a6b6ed@gmail.com>
 <9ff8ca5a-727d-13c3-7c39-6383e00d2edf@infradead.org>
 <ccad7dbf-2136-ea7e-1919-8d94460096c9@gmail.com>
 <2c84903a-ab24-a073-378b-82fe6052e6ac@infradead.org>
 <927a6245-ae8b-ff4b-d668-a819b8351152@citrix.com>
 <34c505d9-9dc6-8982-4875-74dedfc5e0d1@gmail.com>
 <be4448d3-7661-8653-c65f-2a023292b842@citrix.com>
From: PGNet Dev <pgnet.dev@gmail.com>
Message-ID: <dcd8d407-4597-b754-2efa-a81fcd9e8a83@gmail.com>
Date: Sat, 13 May 2017 13:05:22 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101
 Thunderbird/53.0
MIME-Version: 1.0
In-Reply-To: <be4448d3-7661-8653-c65f-2a023292b842@citrix.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.