From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>, Alex <coderain@sdf.org>,
seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>,
Nikolay Nikolov <nickysn@users.sourceforge.net>,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Regression with floppy drive controller
Date: Wed, 21 Aug 2019 09:45:32 +0200 [thread overview]
Message-ID: <6206c058-8fa6-2a19-b76b-dcb5fa260e56@redhat.com> (raw)
In-Reply-To: <20190821064208.eckikvttpdc3zjmd@sirius.home.kraxel.org>
On 21/08/19 08:42, Gerd Hoffmann wrote:
>> So we should use '-cpu Conroe' or '-cpu core2duo' minimum?
> -cpu Conroe for -M isapc is kida silly though ...
>
> Maybe we should simply build seabios with CONFIG_TSC_TIMER=n ?
>
> Using the TSC in a virtual machine is problematic anyway, the
> calibration can be _way_ off on a loaded host, this is why seabios
> prefers the (fixed frequency) pmtimer.
Yeah, that falls back to the PIT which is a good enough source for
SeasBIOS's needs (1 MHz, one third of the pmtimer). It overflows a bit
too easily but it shouldn't be a big deal for users of isapc.
Paolo
next prev parent reply other threads:[~2019-08-21 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 10:25 [Qemu-devel] Regression with floppy drive controller Philippe Mathieu-Daudé
2019-08-20 13:12 ` John Snow
2019-08-20 13:38 ` Philippe Mathieu-Daudé
2019-08-20 14:00 ` Philippe Mathieu-Daudé
2019-08-20 14:36 ` [Qemu-devel] [SeaBIOS] " Dr. David Alan Gilbert
2019-08-20 14:54 ` Philippe Mathieu-Daudé
2019-08-20 15:02 ` Philippe Mathieu-Daudé
2019-08-20 15:04 ` Dr. David Alan Gilbert
2019-08-20 16:21 ` [Qemu-devel] " Philippe Mathieu-Daudé
2019-08-20 20:37 ` Eduardo Habkost
2019-08-21 6:42 ` Gerd Hoffmann
2019-08-21 7:45 ` Paolo Bonzini [this message]
2019-08-21 13:31 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2019-08-22 8:32 ` Gerd Hoffmann
2019-08-22 8:42 ` Gerd Hoffmann
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=6206c058-8fa6-2a19-b76b-dcb5fa260e56@redhat.com \
--to=pbonzini@redhat.com \
--cc=coderain@sdf.org \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=nickysn@users.sourceforge.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).