From: Amit Shah <amit.shah@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
ppandit@redhat.com
Subject: Re: [Qemu-devel] [PATCH] scsi: esp: remove handling of SATN/STOP
Date: Fri, 17 Jun 2016 14:38:12 +0530 [thread overview]
Message-ID: <20160617090812.GB22759@grmbl.mre> (raw)
In-Reply-To: <1466151557-12676-1-git-send-email-pbonzini@redhat.com>
On (Fri) 17 Jun 2016 [10:19:17], Paolo Bonzini wrote:
> The implementation of SATN/STOP is completely busted. The idea
> would be that the next DMA read is for a SCSI message and after
> that the adapter would transition to the command phase.
>
> The recent fix to SATN/STOP broke migration, which is one more
> reason to drop SATN/STOP handling completely. It is only used
> in practice to send 3-byte messages (target number + tag type
> + tag number) for tagged command queuing on adapters that lack
> the SATN3 command, and we do not advertise support for TCQ.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
[...]
> @@ -585,9 +544,12 @@ const VMStateDescription vmstate_esp = {
> VMSTATE_BUFFER(ti_buf, ESPState),
> VMSTATE_UINT32(status, ESPState),
> VMSTATE_UINT32(dma, ESPState),
> - VMSTATE_BUFFER(cmdbuf, ESPState),
> - VMSTATE_UINT32(cmdlen, ESPState),
> - VMSTATE_UINT32(do_cmd, ESPState),
> + /* Used to be cmdbuf, cmdlen, do_cmd, but the implementation
> + * of "Select with ATN and stop" was totally busted.
> + */
> + VMSTATE_UNUSED(16),
> + VMSTATE_UNUSED(4),
> + VMSTATE_UNUSED(1),
Why 1?
Amit
next prev parent reply other threads:[~2016-06-17 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 8:19 [Qemu-devel] [PATCH] scsi: esp: remove handling of SATN/STOP Paolo Bonzini
2016-06-17 9:08 ` Amit Shah [this message]
2016-06-17 9:55 ` Paolo Bonzini
2016-06-17 9:40 ` P J P
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=20160617090812.GB22759@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=hpoussin@reactos.org \
--cc=pbonzini@redhat.com \
--cc=ppandit@redhat.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).