qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: qemu-devel@nongnu.org,  qemu-stable@nongnu.org,  fam@euphon.net,
	pbonzini@redhat.com,  peter.maydell@linaro.org
Subject: Re: [PATCH] hw/scsi/lsi53c895a: bump instruction limit in scripts processing to fix regression
Date: Tue, 16 Jul 2024 09:35:59 +0200	[thread overview]
Message-ID: <87r0bteqlc.fsf@t14.stackframe.org> (raw)
In-Reply-To: <20240715131403.223239-1-f.ebner@proxmox.com> (Fiona Ebner's message of "Mon, 15 Jul 2024 15:14:03 +0200")

Fiona Ebner <f.ebner@proxmox.com> writes:

> Commit 9876359990 ("hw/scsi/lsi53c895a: add timer to scripts
> processing") reduced the maximum allowed instruction count by
> a factor of 100 all the way down to 100.
>
> This causes the "Check Point R81.20 Gaia" appliance [0] to fail to
> boot after fully finishing the installation via the appliance's web
> interface (there is already one reboot before that).
>
> With a limit of 150, the appliance still fails to boot, while with a
> limit of 200, it works. Bump to 500 to fix the regression and be on
> the safe side.
>
> Originally reported in the Proxmox community forum[1].
>
> [0]: https://support.checkpoint.com/results/download/124397
> [1]: https://forum.proxmox.com/threads/149772/post-683459
>
> Cc: qemu-stable@nongnu.org
> Fixes: 9876359990 ("hw/scsi/lsi53c895a: add timer to scripts processing")
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  hw/scsi/lsi53c895a.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/scsi/lsi53c895a.c b/hw/scsi/lsi53c895a.c
> index eb9828dd5e..f1935e5328 100644
> --- a/hw/scsi/lsi53c895a.c
> +++ b/hw/scsi/lsi53c895a.c
> @@ -188,7 +188,7 @@ static const char *names[] = {
>  #define LSI_TAG_VALID     (1 << 16)
>  
>  /* Maximum instructions to process. */
> -#define LSI_MAX_INSN    100
> +#define LSI_MAX_INSN    500
>  
>  typedef struct lsi_request {
>      SCSIRequest *req;

Fine with me - i just picked a random number assuming it
works. Obviously i was wrong :-)

Acked-by: Sven Schnelle <svens@stackframe.org>


  reply	other threads:[~2024-07-16  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 13:14 [PATCH] hw/scsi/lsi53c895a: bump instruction limit in scripts processing to fix regression Fiona Ebner
2024-07-16  7:35 ` Sven Schnelle [this message]
2024-07-16  8:49 ` Paolo Bonzini

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=87r0bteqlc.fsf@t14.stackframe.org \
    --to=svens@stackframe.org \
    --cc=f.ebner@proxmox.com \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).