From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MupoT-00071q-UP
	for qemu-devel@nongnu.org; Mon, 05 Oct 2009 11:49:26 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MupoO-00070T-E3
	for qemu-devel@nongnu.org; Mon, 05 Oct 2009 11:49:25 -0400
Received: from [199.232.76.173] (port=43584 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MupoO-00070M-69
	for qemu-devel@nongnu.org; Mon, 05 Oct 2009 11:49:20 -0400
Received: from dpc6682208002.direcpc.com ([66.82.208.2]:52381
	helo=anvil.third-harmonic.com) by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <john.cooper@third-harmonic.com>) id 1MupoM-00081E-EJ
	for qemu-devel@nongnu.org; Mon, 05 Oct 2009 11:49:20 -0400
Message-ID: <4ACA139B.80201@third-harmonic.com>
Date: Mon, 05 Oct 2009 11:41:15 -0400
From: john cooper <john.cooper@third-harmonic.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] fix virtio_blk serial pci config
	breakage
References: <4AB7A01A.3000206@redhat.com>
	<200909301049.08434.rusty@rustcorp.com.au>
	<4AC2BF9C.9050403@codemonkey.ws>
	<200909302130.33454.rusty@rustcorp.com.au>
	<20090930180443.GB2515@shareable.org>
In-Reply-To: <20090930180443.GB2515@shareable.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, john cooper <john.cooper@redhat.com>, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>, jens.axboe@oracle.com, Vadim Rozenfeld <vrozenfe@redhat.com>

Jamie Lokier wrote:
> (5) When the host's backing driver is itself a disk implementing the
> ATA command, would you ever want the guest to see all details of the
> identity page as close as possible to the host device sometimes?
> I.e. is virtio_blk a way to accelerate block I/O to a host device, or
> a way to abstract it to the bare minimum?

Admittedly most of the data in the identify page
as seen by the host is fodder for the sake of
existing userspace utilities.  So I don't really
see any case where pass-through of host->guest
data is meaningful or useful.  The patch just
follows suit here with a similar mockup of this
data for the guest userland.

-john

-- 
john.cooper@third-harmonic.com