All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: "Alberto Treviño" <alberto@byu.edu>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: LSI: avoid infinite loops
Date: Wed, 7 May 2008 20:42:40 -0300	[thread overview]
Message-ID: <20080507234239.GA28545@dmt> (raw)
In-Reply-To: <200805080021.55113.paul@codesourcery.com>

On Thu, May 08, 2008 at 12:21:54AM +0100, Paul Brook wrote:
> On Thursday 08 May 2008, Marcelo Tosatti wrote:
> > The Windows driver has SCRIPTS code which busy loops on main memory. So
> > give the CPU's a chance to run if that happens.
> 
> I'm kinda surprised this works.  What causes the scripts engine to be 
> restarted?

LSI_ISTAT0_SIGP.

  reply	other threads:[~2008-05-07 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 23:02 [Qemu-devel] LSI: avoid infinite loops Marcelo Tosatti
2008-05-07 23:21 ` [Qemu-devel] " Paul Brook
2008-05-07 23:42   ` Marcelo Tosatti [this message]
2008-05-08  0:39     ` Paul Brook
2008-05-08  0:52       ` Paul Brook
2008-05-08  3:13         ` Marcelo Tosatti
2008-06-19 21:53           ` Marcelo Tosatti
2008-06-19 22:33             ` Paul Brook

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=20080507234239.GA28545@dmt \
    --to=mtosatti@redhat.com \
    --cc=alberto@byu.edu \
    --cc=paul@codesourcery.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.