mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: Valentin Vidic <Valentin.Vidic@CARNet.hr>
Cc: 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
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?
Date: Sat, 13 May 2017 16:17:57 -0700	[thread overview]
Message-ID: <5c0c01ae-775f-55b0-934e-90f81eae8ea3@gmail.com> (raw)
In-Reply-To: <20170513221536.bmijpvmv47pab75c@gavran.carpriv.carnet.hr>

On 5/13/17 3:15 PM, Valentin Vidic wrote:
> Try booting without 'hpet=force,verbose clocksource=hpet' and it should
> select xen by default:

Nope. Well, not quite ...

With both 

	'hpet=force,verbose clocksource=hpet'

removed, I end up with

	cat /sys/devices/system/clocksource/clocksource0/available_clocksource
		tsc xen
	cat /sys/devices/system/clocksource/clocksource0/current_clocksource
		tsc

But with 

	clocksource=xen

*explicitly* added

	cat /sys/devices/system/clocksource/clocksource0/available_clocksource
		tsc xen
	cat /sys/devices/system/clocksource/clocksource0/current_clocksourcexen
		xen

and in *console*, NOT dmesg, output,

	grep -i hpet tmp.txt
		(XEN) ACPI: HPET 9E8298F8, 0038 (r1 SUPERM SMCI--MB  1072009 AMI.        5)
		(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
		(XEN) [VT-D] MSI HPET: 0000:f0:0f.0
		(XEN) Platform timer is 14.318MHz HPET
		[    0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 000000
		[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
		[    0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM SMCI--MB 01072009 AMI. 000000
		[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
		[    8.515245] hpet_acpi_add: no address or irqs in _CRS
		[    8.515245] hpet_acpi_add: no address or irqs in _CRS
		(XEN) [2017-05-13 23:04:27] HVM1 save: HPET



and

	dmesg | grep -i clocksource | grep -v line:
		[    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
		[    0.004000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
		[    0.375709] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
		[    4.656634] clocksource: Switched to clocksource xen
		[    8.912897] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2c94dffea94, max_idle_ns: 440795361700 ns

jiffies, now? hm. no idea where that came from. and why the 'tsc' ?

So I'm still unclear -- is this^ now, correctly "all" using MSI/HPET?

  reply	other threads:[~2017-05-13 23:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  2:30 PGNet Dev
2017-05-13 17:41 ` Randy Dunlap
2017-05-13 18:26   ` PGNet Dev
2017-05-13 19:28     ` Randy Dunlap
2017-05-13 19:38       ` [Xen-devel] " Andrew Cooper
2017-05-13 19:49         ` PGNet Dev
2017-05-13 19:59           ` Andrew Cooper
2017-05-13 20:05             ` PGNet Dev
2017-05-13 20:16               ` Andrew Cooper
2017-05-13 21:07                 ` PGNet Dev
2017-05-14 17:13                 ` Juergen Gross
2017-05-13 20:28               ` Valentin Vidic
2017-05-13 21:06                 ` PGNet Dev
2017-05-13 21:32                   ` Valentin Vidic
2017-05-13 21:58                     ` PGNet Dev
2017-05-13 22:15                       ` Valentin Vidic
2017-05-13 23:17                         ` PGNet Dev [this message]
2017-05-14 15:39                           ` Andrew Cooper
2017-05-14 17:41                             ` Randy Dunlap
2017-05-15 18:06                           ` Austin S. Hemmelgarn
2017-05-17  0:12                             ` PGNet Dev
2017-05-17  0:15                             ` PGNet Dev
2017-05-13 19:45   ` Clemens Ladisch
2017-05-13 19:52     ` PGNet Dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c0c01ae-775f-55b0-934e-90f81eae8ea3@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=Valentin.Vidic@CARNet.hr \
    --cc=andrew.cooper3@citrix.com \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome