From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Andrew Theurer <habanero@linux.vnet.ibm.com>,
Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
seabios <seabios@seabios.org>, ya su <suya94335@gmail.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Kevin O'Connor <kevin@koconnor.net>
Subject: Re: [Qemu-devel] HPET configuration in Seabios
Date: Mon, 29 Aug 2011 14:11:52 +0300 [thread overview]
Message-ID: <4E5B73F8.2040602@redhat.com> (raw)
In-Reply-To: <4E5B7262.4010902@siemens.com>
On 08/29/2011 02:05 PM, Jan Kiszka wrote:
> On 2011-08-29 13:00, Avi Kivity wrote:
> > On 08/29/2011 01:25 PM, Jan Kiszka wrote:
> >>>
> >>> Can't seabios just poke at the hpet itself and see if it exists or not?
> >>>
> >>
> >> Would be hard for the BIOS to guess the locations of the blocks unless
> >> we define the addresses used by QEMU as something like base + hpet_no *
> >> block_size in all cases.
> >>
> >
> > Currently we have a fixed address. We could do:
> >
> > if available in fw_cfg:
> > use that (may indicate no hpet)
> > elif fixed address works:
> > use that
> > else
> > no hpet
>
> Currently, we also only have a single HPET block, but that's just
> because of some QEMU limitations that will vanish sooner or later. Then
> nothing will prevent multiple "-device hpet,base=XXX".
>
Yes, so we should enable the fw_cfg interface before that happens.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-29 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B17C12B.4020300@linux.vnet.ibm.com>
[not found] ` <4B17CC5F.20101@redhat.com>
[not found] ` <CA+tHM2HH437Y4KLmGO+59wvR-TMSacGnxgt5QB8w5LDtJ+p3Xw@mail.gmail.com>
[not found] ` <4E59F15E.6000201@redhat.com>
2011-08-28 18:54 ` [Qemu-devel] windows workload: many ept_violation and mmio exits Alexander Graf
2011-08-28 20:42 ` [Qemu-devel] HPET configuration in Seabios (was: Re: windows workload: many ept_violation and mmio exits) Jan Kiszka
2011-08-28 22:14 ` Kevin O'Connor
2011-08-29 5:32 ` [Qemu-devel] HPET configuration in Seabios Avi Kivity
2011-08-29 10:25 ` Jan Kiszka
2011-08-29 11:00 ` Avi Kivity
2011-08-29 11:05 ` Jan Kiszka
2011-08-29 11:11 ` Avi Kivity [this message]
2011-08-29 11:12 ` Jan Kiszka
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=4E5B73F8.2040602@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=gleb@redhat.com \
--cc=habanero@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=suya94335@gmail.com \
/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).