qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc guest - SCSI
Date: Fri, 3 Aug 2007 22:35:51 +0300	[thread overview]
Message-ID: <f43fc5580708031235w15cc3510oa91b6fb572ccd980@mail.gmail.com> (raw)
In-Reply-To: <6D163EC7-3397-49FA-B0A5-C448E5628AB5@web.de>

I seem to have reverted the patch here:
http://cvs.savannah.gnu.org/viewvc/qemu/qemu/hw/slavio_intctl.c?r1=1.15&r2=1.16

But I still get SCSI errors when using e2fsck with this change.

On 8/3/07, Andreas Färber <andreas.faerber@web.de> wrote:
>
> Am 03.08.2007 um 16:54 schrieb Aurelien Jarno:
>
> >>> I suggest to read the description of the problem from last time:
> >>> http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html
> >>>
> >>> I guess there is still one case when this can happen. The only
> >>> solution
> >>> I see to avoid that is to fix the bug (the problem doesn't occurs on
> >>> real hardware, so the emulation is buggy).
> >>
> >> I tried that patch before ever posting to this list. Like I reported
> >> earlier, if applied I don't get a kernel panic any more but instead
> >> qemu crashes and is "gone". So sadly it didn't fix the issue for me
> >> as is.
> >
> > Which version are you using?
>
> At the time both 0.9.0 and CVS HEAD, today CVS HEAD.
>
> > This patch is supposed to be in the CVS
> > already.
>
> Negative, this is the excerpt from today's hw/slavio_intctl.c around
> line 293:
>
> static void slavio_set_irq(void *opaque, int irq, int level)
> {
>      SLAVIO_INTCTLState *s = opaque;
>      uint32_t mask = 1 << irq;
>      uint32_t pil = s->intbit_to_level[irq];
>
>      DPRINTF("Set cpu %d irq %d -> pil %d level %d\n", s->target_cpu,
> irq, pil,
>              level);
>      if (pil > 0) {
>          if (level) {
>              s->intregm_pending |= mask;
>              s->intreg_pending[s->target_cpu] |= 1 << pil;
>          } else {
>              s->intregm_pending &= ~mask;
>              s->intreg_pending[s->target_cpu] &= ~(1 << pil);
>          }
>          slavio_check_interrupts(s);
>      }
> }
>
> Your referenced patch moves slavio_check_interrupts(s); four lines up
> so is not in CVS.
>
> Andreas
>
>
>

  reply	other threads:[~2007-08-03 19:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  8:45 [Qemu-devel] Sparc guest - SCSI Nigel Horne
2007-08-03 10:27 ` Andreas Färber
2007-08-03 10:42   ` Nigel Horne
2007-08-03 11:30     ` Andreas Färber
2007-08-03 12:02       ` Nigel Horne
2007-08-03 14:21         ` Andreas Färber
2007-08-03 11:52   ` Aurelien Jarno
2007-08-03 13:50     ` Andreas Färber
2007-08-03 14:15       ` Aurelien Jarno
2007-08-03 14:36         ` Andreas Färber
2007-08-03 14:54           ` Aurelien Jarno
2007-08-03 15:31             ` Andreas Färber
2007-08-03 19:35               ` Blue Swirl [this message]
2007-08-04 10:53                 ` Blue Swirl

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=f43fc5580708031235w15cc3510oa91b6fb572ccd980@mail.gmail.com \
    --to=blauwirbel@gmail.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).