From: Jan Kiszka <jan.kiszka@web.de>
To: Juan Quintela <quintela@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [PATCH 0/6] Make hpet a compile time option
Date: Mon, 24 May 2010 22:11:11 +0200 [thread overview]
Message-ID: <4BFADD5F.7010900@web.de> (raw)
In-Reply-To: <m3fx1huq8g.fsf@trasno.mitica>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Juan Quintela wrote:
>>> We already have to disable hpet for 5.4 (1 year ago). It was done with
>>> a local hack because it was supposed that for next big release it would
>>> have been fixed.
>> But this remains a RHEL issue. Redhat decided to compile out features
>> that are unsupported, others seem to handle this differently.
>
> And then, everybody has a different hack to disable the features that
> they don't need. Instead of doing a local hack, we do a patch that
> allows anyone to disable HPET if it sees fit.
So far I only know of precisely one user that wants to disable x86
platform devices at build-time.
>
>>> Here we are, and device is still not fixed, what to do? Another local
>>> patch? Just get upstream to integrate a sane way to disable it and let
>>> in enable by default?
>> Let's start with listing your requirements to no longer disable HPET.
>
> It is not stable at this point in time :-( Running with --no-hpet is
> better than without it in all our testing. If we have to ask/modify
> everything to use --no-hpet, we can also compile-out it.
>
>> That would already help us to asses how long !CONFIG_HPET would actually
>> be of any use at all. I'm yet optimistic that we can resolve most if not
>> all remaining concerns for 0.13 - and CONFIG_HPET would at best be 0.13
>> material anyway.
>
> At this very point in time:
> - it is not stable
Well, that is helpful.
> - lack irq-reinjection when missing ticks
That is more helpful.
I just reworked the RTC regarding this, I guess it will be
straightforward to address it in the HPET too.
>
> (I was not the one debugging/testing this so I don't have more details,
> but can ask for them). So, it is not stable enough yet.
HPET is a fairly small device, a few hundred lines of code, only a few
ugly platform dependencies, but that's it already. I bet it could have
been fixed by now if someone just started by the time the tests reported
"it is not stable enough".
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-05-24 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:18 [Qemu-devel] [PATCH 0/6] Make hpet a compile time option Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 1/6] Create again config-device.h and config.devices.h Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 2/6] Move no_hpet declaration to hpet_emul.h Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 3/6] Move no_hpet test to inside hpet_init() Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 4/6] Make hpet_in_legacy_mode() return 0 for !TARGET_I386 Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 5/6] make hpet_in_legacy_mode() return a bool Juan Quintela
2010-05-24 15:18 ` [Qemu-devel] [PATCH 6/6] Create CONFIG_HPET Juan Quintela
2010-05-24 15:20 ` [Qemu-devel] Re: [PATCH 0/6] Make hpet a compile time option Juan Quintela
2010-05-24 15:43 ` Jan Kiszka
2010-05-24 15:57 ` Juan Quintela
2010-05-24 16:20 ` Jan Kiszka
2010-05-24 18:08 ` Juan Quintela
2010-05-24 20:11 ` Jan Kiszka [this message]
2010-05-24 16:32 ` Paul Brook
2010-05-24 16:49 ` Anthony Liguori
2010-05-24 17:11 ` Paul Brook
2010-05-24 17:37 ` Anthony Liguori
2010-05-24 17:54 ` Juan Quintela
2010-05-24 18:03 ` Anthony Liguori
2010-05-24 18:15 ` Jan Kiszka
2010-05-24 20:16 ` Blue Swirl
2010-05-24 18:10 ` Jan Kiszka
2010-05-25 8:38 ` Paolo Bonzini
2010-05-25 9:05 ` Jan Kiszka
2010-05-25 9:56 ` Paolo Bonzini
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=4BFADD5F.7010900@web.de \
--to=jan.kiszka@web.de \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.