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  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:   Sun, 14 May 2017 00:15:36 +0200
From:   Valentin Vidic <Valentin.Vidic@...Net.hr>
To:     PGNet Dev <pgnet.dev@...il.com>
Cc:     Andrew Cooper <andrew.cooper3@...rix.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        "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 Sat, May 13, 2017 at 02:58:54PM -0700, PGNet Dev wrote:
> Does this perhaps imply that Xen correctly uses HPET
> 
> 	(XEN) [VT-D] MSI HPET: 0000:f0:0f.0
> 	(XEN) Platform timer is 14.318MHz HPET

I think so, yes.

> but that Dom0 does not
> 
> 	current_clocksource
> 		tsc

Try booting without 'hpet=force,verbose clocksource=hpet' and it should
select xen by default:

# dmesg | grep -i clocksource
[   58.944215] Switched to clocksource xen

-- 
Valentin

Powered by blists - more mailing lists