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  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 12:49:32 -0700
From:   PGNet Dev <>
To:     Andrew Cooper <>,
        Randy Dunlap <>,
        "" <>,
        Clemens Ladisch <>,
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?

On 5/13/17 12:38 PM, Andrew Cooper wrote:
> What is the issue here?
> Xen owns (and may use) any HPETs in the system.  They are purposefully
> unavailable to even dom0.

The issue is that, when booting to Xen, hpet is not advertised as an available clocksource, AND reports the hpet boot error pointed out by Randy.


there's discussion there re: 'if HPET is available / not missing'.

It appears to be available only booting to non-Xen.

What specific indication does one look for that Xen's using available hpet?

Powered by blists - more mailing lists