From: Dominique Martinet <asmadeus@codewreck.org>
To: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Steven Sistare <steven.sistare@oracle.com>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
linux@armlinux.org.uk, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, john.stultz@linaro.org,
sboyd@codeaurora.org, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
mingo@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
hpa@zytor.com, douly.fnst@cn.fujitsu.com,
Peter Zijlstra <peterz@infradead.org>,
prarit@redhat.com, feng.tang@intel.com, pmladek@suse.com,
gnomes@lxorguk.ukuu.org.uk, linux-s390@vger.kernel.org,
boris.ostrovsky@oracle.com, jgross@suse.com, pbonzini@redhat.com,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v15 23/26] sched: early boot clock
Date: Fri, 4 Jan 2019 00:43:39 +0100 [thread overview]
Message-ID: <20190103234339.GA17457@nautica> (raw)
In-Reply-To: <CA+CK2bC70pnL0Wimb0xt99J4nNfi8W3zuUHgAk-jsPuOP9jpHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Pavel Tatashin wrote on Thu, Jan 03, 2019:
> Could you please send the config file and qemu arguments that were
> used to reproduce this problem.
Running qemu by hand, nothing fancy e.g. this works:
# qemu-system-x86_64 -m 1G -smp 4 -drive file=/root/kvm-wrapper/disks/f2.img,if=virtio -serial mon:stdio --enable-kvm -cpu Haswell -device virtio-rng-pci -nographic
(used a specific cpu just in case but normally runnning with cpu host on
a skylake machine; can probably go older)
qemu is fedora 29 blend as is:
$ qemu-system-x86_64 --version
QEMU emulator version 3.0.0 (qemu-3.0.0-3.fc29)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
compressed .config attached to the mail, this can likely be trimmed down
some as well but that takes more time for me..
I didn't rebuild the kernel so not 100% sure (comes from
/proc/config.gz) but it should work on a 4.20-rc2 kernel as written in
the first few lines; 857baa87b64 I referred to in another mail was
merged in 4.19-rc1 so anything past that is probably OK to reproduce...
Re-checked today with these exact options (fresh VM start; then suspend
laptop for a bit, then reboot VM):
[ 0.000000] Hypervisor detected: KVM
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[ 2477.907447] kvm-clock: cpu 0, msr 153a4001, primary cpu clock
[ 2477.907448] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[ 2477.907450] tsc: Detected 2592.000 MHz processor
As offered previously, happy to help in any way.
Thanks,
--
Dominique
[-- Attachment #2: config.xz --]
[-- Type: application/octet-stream, Size: 19476 bytes --]
next prev parent reply other threads:[~2019-01-03 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180719205545.16512-1-pasha.tatashin@oracle.com>
[not found] ` <20180719205545.16512-24-pasha.tatashin@oracle.com>
2018-11-06 5:42 ` [Qemu-devel] [PATCH v15 23/26] sched: early boot clock Dominique Martinet
2018-11-06 11:35 ` Steven Sistare
2019-01-02 20:20 ` Salvatore Bonaccorso
2019-01-03 21:28 ` Pavel Tatashin
2019-01-03 23:43 ` Dominique Martinet [this message]
2019-01-07 18:17 ` Pavel Tatashin
2019-01-07 23:48 ` Dominique Martinet
2019-01-08 1:04 ` Pavel Tatashin
2019-01-08 1:09 ` Dominique Martinet
2019-01-26 2:04 ` Jon DeVree
2019-01-26 16:11 ` Pavel Tatashin
2019-01-04 7:30 ` [Qemu-devel] [PATCH v15 23/26] sched: early boot clock (was Re: Bug#918036: linux: uptime after reboot wrong (kvm-clock related?)) Thorsten Glaser
[not found] <154644530361.2390.18185252504260044930.reportbug@ci-busyapps.lan.tarent.de>
[not found] ` <20190102163939.GB13145@eldamar.local>
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=20190103234339.GA17457@nautica \
--to=asmadeus@codewreck.org \
--cc=boris.ostrovsky@oracle.com \
--cc=carnil@debian.org \
--cc=daniel.m.jordan@oracle.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=feng.tang@intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=john.stultz@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pavel.tatashin@microsoft.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sboyd@codeaurora.org \
--cc=schwidefsky@de.ibm.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).