From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38438)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1aXwql-00083G-69
	for qemu-devel@nongnu.org; Mon, 22 Feb 2016 15:12:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1aXwqk-0005d7-C0
	for qemu-devel@nongnu.org; Mon, 22 Feb 2016 15:12:55 -0500
Date: Mon, 22 Feb 2016 22:12:41 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20160222220400-mutt-send-email-mst@redhat.com>
References: <1456144729-17196-1-git-send-email-mst@redhat.com>
	<1456151216.29896.63.camel@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1456151216.29896.63.camel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] fw-cfg: support writeable blobs
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: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, Xiao Guangrong <guangrong.xiao@linux.intel.com>, Eduardo Habkost <ehabkost@redhat.com>, Igor Mammedov <imammedo@redhat.com>, "Gabriel L. Somlo" <somlo@cmu.edu>, qemu-devel@nongnu.org, Michael Walle <michael@walle.cc>, Kevin O'Connor <kevin@koconnor.net>, qemu-arm@nongnu.org, Shannon Zhao <zhaoshenglong@huawei.com>, Paolo Bonzini <pbonzini@redhat.com>, Richard Henderson <rth@twiddle.net>

On Mon, Feb 22, 2016 at 03:26:56PM +0100, Gerd Hoffmann wrote:
> On Mo, 2016-02-22 at 14:41 +0200, Michael S. Tsirkin wrote:
> > Useful to send guest data back to QEMU.
> 
> Use case?
> 
> cheers,
>   Gerd

VM GEN ID at least wants to pass address of some blob
in guest memory to host.

Apparently, that's also useful for nvdimm.

A reasonable way to do that seems to be to write it into
fw cfg file, this way it's also migrated automatically.

-- 
MST