qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Check if the i8254 timer is active before deactivating it
Date: Mon, 26 Jan 2009 14:33:01 -0600	[thread overview]
Message-ID: <497E1DFD.4070607@us.ibm.com> (raw)
In-Reply-To: <1232988117-8935-1-git-send-email-agraf@suse.de>

Alexander Graf wrote:
> The HPET emulation can disable the i8254 when the HPET is
> in legacy mode, thus emulating the i8254's behavior.
>
> But if it does, the i8254 doesn't have to be running, so
> let's check to see if the timer works and not disable it
> if it's not.
>
> This fixes a segmentation fault when running Mac OS X as
> guest os.
>   

So the HPET works with Mac OS X with this patch?  That's good to know 
since there was a fair bit of change from your original patch.

> Signed-off-by: Alexander Graf <agraf@suse.de>
>   

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>  hw/i8254.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/hw/i8254.c b/hw/i8254.c
> index a4a1efe..44e4531 100644
> --- a/hw/i8254.c
> +++ b/hw/i8254.c
> @@ -467,7 +467,8 @@ static void pit_reset(void *opaque)
>  void hpet_pit_disable(void) {
>      PITChannelState *s;
>      s = &pit_state.channels[0];
> -    qemu_del_timer(s->irq_timer);
> +    if (s->irq_timer)
> +        qemu_del_timer(s->irq_timer);
>  }
>  
>  /* When HPET is reset or leaving legacy mode, it must reenable i8254
>   

  reply	other threads:[~2009-01-26 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 16:41 [Qemu-devel] [PATCH] Check if the i8254 timer is active before deactivating it Alexander Graf
2009-01-26 20:33 ` Anthony Liguori [this message]
2009-01-27  7:18   ` Alexander Graf
2009-01-27  7:37     ` Alexander Graf

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=497E1DFD.4070607@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.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).