From: Gleb Natapov <gleb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 6/6] suspend: make rtc alarm wakeup the guest.
Date: Thu, 9 Feb 2012 10:56:58 +0200 [thread overview]
Message-ID: <20120209085658.GE18866@redhat.com> (raw)
In-Reply-To: <1328698819-31269-7-git-send-email-kraxel@redhat.com>
On Wed, Feb 08, 2012 at 12:00:19PM +0100, Gerd Hoffmann wrote:
> Add a 'wakeup' property to the mc146818rtc. It is on by default.
> When enabled the rtc will wake up the guest when the alarm fires.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/mc146818rtc.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/hw/mc146818rtc.c b/hw/mc146818rtc.c
> index 314ed52..3b912c6 100644
> --- a/hw/mc146818rtc.c
> +++ b/hw/mc146818rtc.c
> @@ -86,6 +86,7 @@ typedef struct RTCState {
> uint8_t cmos_index;
> struct tm current_tm;
> int32_t base_year;
> + uint32_t wakeup;
> qemu_irq irq;
> qemu_irq sqw_irq;
> int it_shift;
> @@ -437,6 +438,9 @@ static void rtc_update_second2(void *opaque)
>
> s->cmos_data[RTC_REG_C] |= REG_C_AF;
> if (s->cmos_data[RTC_REG_B] & REG_B_AIE) {
> + if (s->wakeup) {
> + qemu_system_wakeup_request();
> + }
RTC should do wakeup only if RTC_EN bit is set pm1en.
> qemu_irq_raise(s->irq);
> s->cmos_data[RTC_REG_C] |= REG_C_IRQF;
> }
> @@ -725,6 +729,7 @@ static Property mc146818rtc_properties[] = {
> DEFINE_PROP_INT32("base_year", RTCState, base_year, 1980),
> DEFINE_PROP_LOSTTICKPOLICY("lost_tick_policy", RTCState,
> lost_tick_policy, LOST_TICK_DISCARD),
> + DEFINE_PROP_UINT32("wakeup", RTCState, wakeup, 1),
> DEFINE_PROP_END_OF_LIST(),
> };
>
> --
> 1.7.1
>
>
--
Gleb.
next prev parent reply other threads:[~2012-02-09 8:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 11:00 [Qemu-devel] [PATCH v3 0/6] initial suspend support Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 1/6] suspend: add infrastructure Gerd Hoffmann
2012-02-09 8:48 ` Gleb Natapov
2012-02-09 10:45 ` Gerd Hoffmann
2012-02-09 11:19 ` Gleb Natapov
2012-02-09 12:02 ` Gerd Hoffmann
2012-02-09 12:37 ` Gleb Natapov
2012-02-09 12:46 ` Gerd Hoffmann
2012-02-09 13:17 ` Gleb Natapov
2012-02-09 13:29 ` Gerd Hoffmann
2012-02-09 16:00 ` Gerd Hoffmann
2012-02-09 16:05 ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure Gerd Hoffmann
2012-02-09 8:53 ` Gleb Natapov
2012-02-09 10:51 ` Gerd Hoffmann
2012-02-09 11:14 ` Gleb Natapov
2012-02-09 11:13 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2012-02-09 11:17 ` [Qemu-devel] " Paolo Bonzini
2012-02-09 12:31 ` Gleb Natapov
2012-02-09 12:47 ` Paolo Bonzini
2012-02-09 12:53 ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 3/6] suspend: add system_wakeup monitor command Gerd Hoffmann
2012-02-09 8:54 ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 4/6] suspend: make ps/2 devices wakeup the guest Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 5/6] suspend: make serial ports " Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 6/6] suspend: make rtc alarm " Gerd Hoffmann
2012-02-09 8:56 ` Gleb Natapov [this message]
2012-02-09 12:00 ` Gerd Hoffmann
2012-02-09 12:24 ` Gleb Natapov
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=20120209085658.GE18866@redhat.com \
--to=gleb@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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).