From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53312)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1V19id-0000XM-Ch
	for qemu-devel@nongnu.org; Mon, 22 Jul 2013 02:35:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1V19ib-00056q-KF
	for qemu-devel@nongnu.org; Mon, 22 Jul 2013 02:35:38 -0400
Message-ID: <1374474925.3916.34.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Mon, 22 Jul 2013 16:35:25 +1000
In-Reply-To: <51ECD190.60700@redhat.com>
References: <1374401042-18511-1-git-send-email-aik@ozlabs.ru>
	<1374442491.3916.2.camel@pasglop> <51EC7AC9.3080306@ozlabs.ru>
	<1374452612.3916.17.camel@pasglop> <51EC8381.4020801@ozlabs.ru>
	<1374455044.3916.27.camel@pasglop> <51ECD190.60700@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH] spapr-vscsi: add task management
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Alexey Kardashevskiy <aik@ozlabs.ru>, Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org, Paul Mackerras <paulus@samba.org>, qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>

On Mon, 2013-07-22 at 08:30 +0200, Paolo Bonzini wrote:
> I suggest you check in the relevant part of the vscsi spec how you are
> supposed to send back errors ("FUNCTION REJECTED", "INCORRECT LUN").
> Once you do that, implementing the "query" TMFs is trivial.

The vscsi spec is just the transport around SRP, so not very useful,
mostly it's the SRP spec that matters. IE. VSCSI is just SRP inside a
special hypervisor tube :-)

Cheers,
Ben.