From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=43763 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1ObDMD-0006Qn-4R
	for qemu-devel@nongnu.org; Tue, 20 Jul 2010 09:59:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <rjones@redhat.com>) id 1ObDM4-00058x-6q
	for qemu-devel@nongnu.org; Tue, 20 Jul 2010 09:59:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:25845)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <rjones@redhat.com>) id 1ObDM4-00058r-0N
	for qemu-devel@nongnu.org; Tue, 20 Jul 2010 09:59:32 -0400
Date: Tue, 20 Jul 2010 14:59:27 +0100
From: "Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] Question about qemu firmware configuration
	(fw_cfg) device
Message-ID: <20100720135927.GB6143@amd.home.annexia.org>
References: <269D196D-8CE8-4E24-8EE1-39756AC55F7F@suse.de>
	<20100718200942.GL13194@amd.home.annexia.org>
	<44FD4F00-843D-41C8-B21A-148D16745015@suse.de>
	<20100719062356.GU4689@redhat.com>
	<20100719072802.GO13194@amd.home.annexia.org>
	<20100719073312.GY4689@redhat.com>
	<4E9BBBA5-F2D1-4485-AFD3-8D6FDE3A3CCC@suse.de>
	<20100719075110.GB4689@redhat.com>
	<20100720131516.GC5439@shareable.org>
	<20100720134028.GF27238@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100720134028.GF27238@redhat.com>
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.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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org

On Tue, Jul 20, 2010 at 04:40:28PM +0300, Gleb Natapov wrote:
> Which remind me that ad-hoc DMA interface should be discoverable by a
> guest.

Judging by 'git annotate' this interface has already been extended 4
times without requiring this to be discoverable.  However I will add
an extra config bitmask which guests can fetch in my next version.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v