lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 13 May 2017 20:38:33 +0100
From:   Andrew Cooper <andrew.cooper3@...rix.com>
To:     Randy Dunlap <rdunlap@...radead.org>, pgnet.dev@...il.com,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Clemens Ladisch <clemens@...isch.de>,
        xen-devel@...ts.xenproject.org
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ