From: Paolo Bonzini <pbonzini@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] scsi: esp: Improve consistency of RSTAT, RSEQ, and RINTR
Date: Thu, 29 Nov 2018 18:53:07 +0100 [thread overview]
Message-ID: <1012f9d2-426d-d120-8ec5-2afe8eec4578@redhat.com> (raw)
In-Reply-To: <20181129173845.GA2929@roeck-us.net>
On 29/11/18 18:38, Guenter Roeck wrote:
> This looks much cleaner than the previous patch and at the same time
> identifies the problem. Enabling the new trace shows that the condition
> is seen on a regular basis (on average 2-3 times per boot test with
> qemu-system-hppa if the test does nothing but shut down immediately).
Yes, this looks very nice. I'll queue it if Mark reports that it works,
with just s/_esp_command_complete/esp_report_command_complete/.
Paolo
next prev parent reply other threads:[~2018-11-29 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:56 [Qemu-devel] [PATCH 1/2] esp-pci: Fix status register write erase control Guenter Roeck
2018-11-28 21:56 ` [Qemu-devel] [PATCH 2/2] scsi: esp: Improve consistency of RSTAT, RSEQ, and RINTR Guenter Roeck
2018-11-29 9:58 ` Paolo Bonzini
2018-11-29 11:56 ` Mark Cave-Ayland
2018-11-29 15:42 ` Guenter Roeck
2018-11-29 17:38 ` Guenter Roeck
2018-11-29 17:53 ` Paolo Bonzini [this message]
2018-11-29 18:07 ` Mark Cave-Ayland
2018-11-29 19:00 ` Guenter Roeck
2018-11-29 19:33 ` Mark Cave-Ayland
2018-11-29 21:26 ` Guenter Roeck
2018-11-29 18:34 ` Mark Cave-Ayland
2018-11-29 19:07 ` Guenter Roeck
2018-11-29 19:38 ` Mark Cave-Ayland
2018-11-29 14:18 ` Guenter Roeck
2018-11-29 9:58 ` [Qemu-devel] [PATCH 1/2] esp-pci: Fix status register write erase control 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=1012f9d2-426d-d120-8ec5-2afe8eec4578@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=linux@roeck-us.net \
--cc=mark.cave-ayland@ilande.co.uk \
--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).