All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [5026] i386: fix isapc machine
Date: Wed, 20 Aug 2008 16:28:29 +0200	[thread overview]
Message-ID: <48AC2A0D.4020602@siemens.com> (raw)
In-Reply-To: <E1KVQk6-0002JW-LI@cvs.savannah.gnu.org>

Aurelien Jarno wrote:
> Revision: 5026
>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5026
> Author:   aurel32
> Date:     2008-08-19 12:55:20 +0000 (Tue, 19 Aug 2008)
> 
> Log Message:
> -----------
> i386: fix isapc machine
> 
> - cirrus vga: enable graphic console
> - pc: don't use apic for interrupts on ISA machine
> 

...

> Modified: trunk/hw/pc.c
> ===================================================================
> --- trunk/hw/pc.c	2008-08-18 18:00:31 UTC (rev 5025)
> +++ trunk/hw/pc.c	2008-08-19 12:55:20 UTC (rev 5026)
> @@ -121,10 +121,14 @@
>      if (!level)
>          return;
>  
> -    while (env) {
> -        if (apic_accept_pic_intr(env))
> -            apic_local_deliver(env, APIC_LINT0);
> -        env = env->next_cpu;
> +    if (env->apic_state) {
> +        while (env) {
> +            if (apic_accept_pic_intr(env))
> +                apic_local_deliver(env, APIC_LINT0);
> +            env = env->next_cpu;
> +        }
> +    } else {
> +        cpu_interrupt(env, CPU_INTERRUPT_HARD);
>      }
>  }

Considering our recent experience with the APIC path, and also when
looking at old qemu versions, just asserting CPU_INTERRUPT_HARD won't be
enough. We also need cpu_reset_interrupt in the (!level) case. Will post
a patch, along with a rebased version for the APIC fix.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

      reply	other threads:[~2008-08-20 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 12:55 [Qemu-devel] [5026] i386: fix isapc machine Aurelien Jarno
2008-08-20 14:28 ` Jan Kiszka [this message]

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=48AC2A0D.4020602@siemens.com \
    --to=jan.kiszka@siemens.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 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.