qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,  Fam Zheng <fam@euphon.net>,
	 Peter Maydell <peter.maydell@linaro.org>,
	 qemu-devel@nongnu.org,  deller@gmx.de
Subject: Re: [PATCH] hw/scsi/lsi53c895a: add timer to scripts processing
Date: Fri, 01 Mar 2024 06:57:17 +0100	[thread overview]
Message-ID: <871q8uxznm.fsf@t14.stackframe.org> (raw)
In-Reply-To: <f5fe5ee1-fd43-7cf8-73bc-d0eef4b5eb98@eik.bme.hu> (BALATON Zoltan's message of "Fri, 1 Mar 2024 00:01:24 +0100 (CET)")

BALATON Zoltan <balaton@eik.bme.hu> writes:

> On Thu, 29 Feb 2024, Sven Schnelle wrote:
>> BALATON Zoltan <balaton@eik.bme.hu> writes:
>> Yes, i changed it to describe the new method:
>>
>>    /*
>>     * Some windows drivers make the device spin waiting for a memory location
>>     * to change. If we have executed more than LSI_MAX_INSN instructions then
>>     * assume this is the case and start a timer. Until the timer fires, the
>>     * host CPU has a chance to run and change the memory location.
>
> Is that the host or guest CPU? I thought the guest vcpu needs to get a
> chance to do something about this but maybe I did not get the problem
> at all.

Of course it's the guest CPU. I'll wait for other review comments and
fix it in the next version.

Thanks!
Sven


      reply	other threads:[~2024-03-01  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 19:30 [PATCH] hw/scsi/lsi53c895a: add timer to scripts processing Sven Schnelle
2024-02-29 20:01 ` BALATON Zoltan
2024-02-29 20:19   ` Sven Schnelle
2024-02-29 23:01     ` BALATON Zoltan
2024-03-01  5:57       ` Sven Schnelle [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=871q8uxznm.fsf@t14.stackframe.org \
    --to=svens@stackframe.org \
    --cc=balaton@eik.bme.hu \
    --cc=deller@gmx.de \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).