From: Thomas Huth <thuth@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael S Tsirkin <mst@redhat.com>,
qemu-devel@nongnu.org, Bernhard Beschow <shentey@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH 4/6] hw/rtc/mc146818rtc: Add a property for the availability of the slew tick policy
Date: Mon, 9 Jan 2023 21:12:29 +0100 [thread overview]
Message-ID: <045df8de-c9c4-b68c-29f6-1893724574e4@redhat.com> (raw)
In-Reply-To: <1bd2f34b-2364-1ce7-a3f4-946e76594344@ilande.co.uk>
On 04/01/2023 09.55, Mark Cave-Ayland wrote:
> On 03/01/2023 08:47, Thomas Huth wrote:
>
>> We want to get rid of the "#ifdef TARGET_I386" statements in the mc146818
>> code, so we need a different way to decide whether the slew tick policy
>> is available or not. Introduce a new property "slew-tick-policy-available"
>> which can be set by the machines that support this tick policy.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> include/hw/rtc/mc146818rtc.h | 1 +
>> hw/i386/pc_piix.c | 1 +
>> hw/isa/lpc_ich9.c | 1 +
>> hw/isa/piix3.c | 1 +
>> hw/rtc/mc146818rtc.c | 16 ++++++++++------
>> 5 files changed, 14 insertions(+), 6 deletions(-)
>>
>> diff --git a/include/hw/rtc/mc146818rtc.h b/include/hw/rtc/mc146818rtc.h
>> index 1db0fcee92..54af63d091 100644
>> --- a/include/hw/rtc/mc146818rtc.h
>> +++ b/include/hw/rtc/mc146818rtc.h
>> @@ -45,6 +45,7 @@ struct RTCState {
>> QEMUTimer *coalesced_timer;
>> Notifier clock_reset_notifier;
>> LostTickPolicy lost_tick_policy;
>> + bool slew_tick_policy_available;
>> Notifier suspend_notifier;
>> QLIST_ENTRY(RTCState) link;
>> };
>> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
>> index bc9ea8cdae..382c6add3b 100644
>> --- a/hw/i386/pc_piix.c
>> +++ b/hw/i386/pc_piix.c
>> @@ -233,6 +233,7 @@ static void pc_init1(MachineState *machine,
>> rtc_state = isa_new(TYPE_MC146818_RTC);
>> qdev_prop_set_int32(DEVICE(rtc_state), "base_year", 2000);
>> + qdev_prop_set_bit(DEVICE(rtc_state),
>> "slew-tick-policy-available", true);
>> isa_realize_and_unref(rtc_state, isa_bus, &error_fatal);
>> i8257_dma_init(isa_bus, 0);
>> diff --git a/hw/isa/lpc_ich9.c b/hw/isa/lpc_ich9.c
>> index 498175c1cc..aeab4d8549 100644
>> --- a/hw/isa/lpc_ich9.c
>> +++ b/hw/isa/lpc_ich9.c
>> @@ -733,6 +733,7 @@ static void ich9_lpc_realize(PCIDevice *d, Error **errp)
>> /* RTC */
>> qdev_prop_set_int32(DEVICE(&lpc->rtc), "base_year", 2000);
>> + qdev_prop_set_bit(DEVICE(&lpc->rtc), "slew-tick-policy-available",
>> true);
>> if (!qdev_realize(DEVICE(&lpc->rtc), BUS(isa_bus), errp)) {
>> return;
>> }
>> diff --git a/hw/isa/piix3.c b/hw/isa/piix3.c
>> index c68e51ddad..825b1cbee2 100644
>> --- a/hw/isa/piix3.c
>> +++ b/hw/isa/piix3.c
>> @@ -316,6 +316,7 @@ static void pci_piix3_realize(PCIDevice *dev, Error
>> **errp)
>> /* RTC */
>> qdev_prop_set_int32(DEVICE(&d->rtc), "base_year", 2000);
>> + qdev_prop_set_bit(DEVICE(&d->rtc), "slew-tick-policy-available", true);
>> if (!qdev_realize(DEVICE(&d->rtc), BUS(isa_bus), errp)) {
>> return;
>> }
>> diff --git a/hw/rtc/mc146818rtc.c b/hw/rtc/mc146818rtc.c
>> index 947d68c257..86381a74c3 100644
>> --- a/hw/rtc/mc146818rtc.c
>> +++ b/hw/rtc/mc146818rtc.c
>> @@ -922,14 +922,16 @@ static void rtc_realizefn(DeviceState *dev, Error
>> **errp)
>> rtc_set_date_from_host(isadev);
>> switch (s->lost_tick_policy) {
>> -#ifdef TARGET_I386
>> - case LOST_TICK_POLICY_SLEW:
>> - s->coalesced_timer =
>> - timer_new_ns(rtc_clock, rtc_coalesced_timer, s);
>> - break;
>> -#endif
>> case LOST_TICK_POLICY_DISCARD:
>> break;
>> + case LOST_TICK_POLICY_SLEW:
>> +#ifdef TARGET_I386
>> + if (s->slew_tick_policy_available) {
>> + s->coalesced_timer = timer_new_ns(rtc_clock,
>> rtc_coalesced_timer, s);
>> + break;
>> + }
>> +#endif
>> + /* fallthrough */
>> default:
>> error_setg(errp, "Invalid lost tick policy.");
>> return;
>> @@ -989,6 +991,8 @@ static Property mc146818rtc_properties[] = {
>> DEFINE_PROP_UINT8("irq", RTCState, isairq, RTC_ISA_IRQ),
>> DEFINE_PROP_LOSTTICKPOLICY("lost_tick_policy", RTCState,
>> lost_tick_policy, LOST_TICK_POLICY_DISCARD),
>> + DEFINE_PROP_BOOL("slew-tick-policy-available", RTCState,
>> + slew_tick_policy_available, false),
>> DEFINE_PROP_END_OF_LIST(),
>> };
>
> My first thought when looking at the new "slew-tick-policy-available"
> property introduced above was that it seems to overlap with the
> "lost_tick_policy" property defined just above it using
> DEFINE_PROP_LOSTTICKPOLICY().
You've got a point here ... it's a little bit ugly that we have two
user-visible properties for the lost tick policy now...
> This made me wonder if a better approach here would be to move the logic
> that determines if LOST_TICK_POLICY_SLEW is available into the
> "lost_tick_policy" property setter defined at
> https://gitlab.com/qemu-project/qemu/-/blob/master/hw/core/qdev-properties-system.c#L558.
>
> If you look at the code directly below the link above you can see how
> set_blocksize() overrides the .set function for qdev_prop_blocksize to
> provide additional validation, which is similar to what we are trying to do
> here.
>
> I think it may be possible to come up with a similar solution for
> qdev_prop_losttickpolicy which makes use of the logic you suggested before i.e.
>
> MachineState *ms = MACHINE(qdev_get_machine());
>
> if (!object_dynamic_cast(OBJECT(ms), TYPE_X86_MACHINE)) {
> ....
> }
>
> which can then emit a suitable warning or return an error accordingly. A
> quick glance at hw/core/qdev-properties-system.c suggests there are a number
> of similar examples showing how this could be done.
Thanks, I like that idea! I'll give it a try!
Thomas
next prev parent reply other threads:[~2023-01-09 20:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 8:47 [PATCH 0/6] mc146818rtc related clean-ups and improvements Thomas Huth
2023-01-03 8:47 ` [PATCH 1/6] hw/i386/pc: Create RTC controllers in south bridges Thomas Huth
2023-01-03 8:47 ` [PATCH 2/6] hw/i386/pc: No need for rtc_state to be an out-parameter Thomas Huth
2023-01-03 13:11 ` Philippe Mathieu-Daudé
2023-01-03 8:47 ` [PATCH 3/6] hw/intc: Extract the IRQ counting functions into a separate file Thomas Huth
2023-01-03 12:55 ` Bernhard Beschow
2023-01-03 8:47 ` [PATCH 4/6] hw/rtc/mc146818rtc: Add a property for the availability of the slew tick policy Thomas Huth
2023-01-03 13:10 ` Philippe Mathieu-Daudé
2023-01-03 13:32 ` Bernhard Beschow
2023-01-03 13:46 ` Bernhard Beschow
2023-01-03 15:00 ` Bernhard Beschow
2023-01-04 8:55 ` Mark Cave-Ayland
2023-01-09 20:12 ` Thomas Huth [this message]
2023-01-09 20:53 ` B
2023-01-10 7:52 ` Thomas Huth
2023-01-03 8:48 ` [PATCH 5/6] hw/rtc/mc146818rtc: Make the mc146818 RTC device target independent Thomas Huth
2023-01-03 12:58 ` Bernhard Beschow
2023-01-03 8:48 ` [PATCH 6/6] softmmu/rtc: Emit warning when using driftfix=slew on systems without mc146818 Thomas Huth
2023-01-03 13:08 ` Philippe Mathieu-Daudé
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=045df8de-c9c4-b68c-29f6-1893724574e4@redhat.com \
--to=thuth@redhat.com \
--cc=aurelien@aurel32.net \
--cc=balaton@eik.bme.hu \
--cc=eduardo@habkost.net \
--cc=hpoussin@reactos.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@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).