From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755986AbcBJBib (ORCPT <rfc822;w@1wt.eu>);
	Tue, 9 Feb 2016 20:38:31 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:33317 "EHLO
	mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753609AbcBJBi3 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Feb 2016 20:38:29 -0500
Date: Tue, 9 Feb 2016 17:38:28 -0800
From: Greg KH <gregkh@linuxfoundation.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: "Gabriel L. Somlo" <somlo@cmu.edu>, robh+dt@kernel.org, pawel.moll@arm.com,
        mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
        galak@codeaurora.org, arnd@arndb.de, lersek@redhat.com,
        ralf@linux-mips.org, rmk+kernel@arm.linux.org.uk, eric@anholt.net,
        hanjun.guo@linaro.org, zajec5@gmail.com, sudeep.holla@arm.com,
        agross@codeaurora.org, linux-api@vger.kernel.org,
        linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
        qemu-devel@nongnu.org, mst@redhat.com, imammedo@redhat.com,
        peter.maydell@linaro.org, leif.lindholm@linaro.org,
        ard.biesheuvel@linaro.org, pbonzini@redhat.com, kraxel@redhat.com,
        ehabkost@redhat.com, luto@amacapital.net, stefanha@gmail.com,
        revol@free.fr, rth@twiddle.net
Subject: Re: [PATCH v8 0/4] SysFS driver for QEMU fw_cfg device
Message-ID: <20160210013828.GA32439@kroah.com>
References: <1453990994-17801-1-git-send-email-somlo@cmu.edu>
 <20160203224729.GB15385@codeblueprint.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160203224729.GB15385@codeblueprint.co.uk>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 03, 2016 at 10:47:29PM +0000, Matt Fleming wrote:
> On Thu, 28 Jan, at 09:23:10AM, Gabriel L. Somlo wrote:
> > From: "Gabriel Somlo" <somlo@cmu.edu>
> > 
> > Allow access to QEMU firmware blobs, passed into the guest VM via
> > the fw_cfg device, through SysFS entries. Blob meta-data (e.g. name,
> > size, and fw_cfg key), as well as the raw binary blob data may be
> > accessed.
> > 
> > The SysFS access location is /sys/firmware/qemu_fw_cfg/... and was
> > selected based on overall similarity to the type of information
> > exposed under /sys/firmware/dmi/entries/...
> > 
> > This functionality is primarily intended to serve as a host->guest
> > configuration data transfer mechanism that is both:
> > 
> >         - asynchronous: the host doesn't need to wait for the guest
> >                         to be ready to accept data (e.g., by starting
> >                         an agent daemon)
> > 
> >         - out-of-band:  there is no need to commandeer a guest element
> >                         normally visible and available to the guest user
> >                         (e.g., kernel cmdline, mounting floppy/cdrom, etc.)
> > 
> > QEMU now allows arbitrary fw_cfg blobs to be added via the command line,
> > so it would be nice to make them easy to retrieve from within the guest
> > OS, and the niceset and easiest way I can think of is
> > 
> >         cat /sys/firmware/qemu-fw-cfg/.../<some-blob-name>/raw
> > 
> > New since v7:
> > 
> > 	- kbuild testbot complained about a warning on ia64, so limit
> > 	  the availability of fw_cfg in Kconfig to only architectures
> > 	  on which QEMU makes it available, which include:
> > 
> > 		(ARM || ARM64 || PPC_PMAC || SPARC || X86)
> 
> This is looking pretty good now. Does anyone have remaining
> objections before this gets merged?

All now merged in my tree, thanks.

greg k-h

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v8 0/4] SysFS driver for QEMU fw_cfg device
Date: Tue, 9 Feb 2016 17:38:28 -0800
Message-ID: <20160210013828.GA32439@kroah.com>
References: <1453990994-17801-1-git-send-email-somlo@cmu.edu>
	<20160203224729.GB15385@codeblueprint.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
Content-Disposition: inline
In-Reply-To: <20160203224729.GB15385@codeblueprint.co.uk>
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>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: mark.rutland@arm.com, peter.maydell@linaro.org, mst@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org, eric@anholt.net, kraxel@redhat.com, agross@codeaurora.org, pawel.moll@arm.com, zajec5@gmail.com, rmk+kernel@arm.linux.org.uk, lersek@redhat.com, devicetree@vger.kernel.org, ehabkost@redhat.com, arnd@arndb.de, ijc+devicetree@hellion.org.uk, "Gabriel L. Somlo" <somlo@cmu.edu>, galak@codeaurora.org, leif.lindholm@linaro.org, robh+dt@kernel.org, pbonzini@redhat.com, rth@twiddle.net, ard.biesheuvel@linaro.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, luto@amacapital.net, hanjun.guo@linaro.org, sudeep.holla@arm.com, imammedo@redhat.com, revol@free.fr
List-Id: devicetree@vger.kernel.org

On Wed, Feb 03, 2016 at 10:47:29PM +0000, Matt Fleming wrote:
> On Thu, 28 Jan, at 09:23:10AM, Gabriel L. Somlo wrote:
> > From: "Gabriel Somlo" <somlo@cmu.edu>
> > 
> > Allow access to QEMU firmware blobs, passed into the guest VM via
> > the fw_cfg device, through SysFS entries. Blob meta-data (e.g. name,
> > size, and fw_cfg key), as well as the raw binary blob data may be
> > accessed.
> > 
> > The SysFS access location is /sys/firmware/qemu_fw_cfg/... and was
> > selected based on overall similarity to the type of information
> > exposed under /sys/firmware/dmi/entries/...
> > 
> > This functionality is primarily intended to serve as a host->guest
> > configuration data transfer mechanism that is both:
> > 
> >         - asynchronous: the host doesn't need to wait for the guest
> >                         to be ready to accept data (e.g., by starting
> >                         an agent daemon)
> > 
> >         - out-of-band:  there is no need to commandeer a guest element
> >                         normally visible and available to the guest user
> >                         (e.g., kernel cmdline, mounting floppy/cdrom, etc.)
> > 
> > QEMU now allows arbitrary fw_cfg blobs to be added via the command line,
> > so it would be nice to make them easy to retrieve from within the guest
> > OS, and the niceset and easiest way I can think of is
> > 
> >         cat /sys/firmware/qemu-fw-cfg/.../<some-blob-name>/raw
> > 
> > New since v7:
> > 
> > 	- kbuild testbot complained about a warning on ia64, so limit
> > 	  the availability of fw_cfg in Kconfig to only architectures
> > 	  on which QEMU makes it available, which include:
> > 
> > 		(ARM || ARM64 || PPC_PMAC || SPARC || X86)
> 
> This is looking pretty good now. Does anyone have remaining
> objections before this gets merged?

All now merged in my tree, thanks.

greg k-h

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50299)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gregkh@linuxfoundation.org>) id 1aTJjl-0006VC-JJ
	for qemu-devel@nongnu.org; Tue, 09 Feb 2016 20:38:34 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gregkh@linuxfoundation.org>) id 1aTJji-0001iU-AW
	for qemu-devel@nongnu.org; Tue, 09 Feb 2016 20:38:33 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:43271)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gregkh@linuxfoundation.org>) id 1aTJji-0001iI-4T
	for qemu-devel@nongnu.org; Tue, 09 Feb 2016 20:38:30 -0500
Date: Tue, 9 Feb 2016 17:38:28 -0800
From: Greg KH <gregkh@linuxfoundation.org>
Message-ID: <20160210013828.GA32439@kroah.com>
References: <1453990994-17801-1-git-send-email-somlo@cmu.edu>
	<20160203224729.GB15385@codeblueprint.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160203224729.GB15385@codeblueprint.co.uk>
Subject: Re: [Qemu-devel] [PATCH v8 0/4] SysFS driver for QEMU fw_cfg device
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: Matt Fleming <matt@codeblueprint.co.uk>
Cc: mark.rutland@arm.com, peter.maydell@linaro.org, mst@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org, eric@anholt.net, kraxel@redhat.com, agross@codeaurora.org, pawel.moll@arm.com, zajec5@gmail.com, rmk+kernel@arm.linux.org.uk, lersek@redhat.com, devicetree@vger.kernel.org, ehabkost@redhat.com, arnd@arndb.de, ijc+devicetree@hellion.org.uk, "Gabriel L. Somlo" <somlo@cmu.edu>, galak@codeaurora.org, leif.lindholm@linaro.org, robh+dt@kernel.org, pbonzini@redhat.com, rth@twiddle.net, ard.biesheuvel@linaro.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, luto@amacapital.net, hanjun.guo@linaro.org, sudeep.holla@arm.com, imammedo@redhat.com, revol@free.fr

On Wed, Feb 03, 2016 at 10:47:29PM +0000, Matt Fleming wrote:
> On Thu, 28 Jan, at 09:23:10AM, Gabriel L. Somlo wrote:
> > From: "Gabriel Somlo" <somlo@cmu.edu>
> > 
> > Allow access to QEMU firmware blobs, passed into the guest VM via
> > the fw_cfg device, through SysFS entries. Blob meta-data (e.g. name,
> > size, and fw_cfg key), as well as the raw binary blob data may be
> > accessed.
> > 
> > The SysFS access location is /sys/firmware/qemu_fw_cfg/... and was
> > selected based on overall similarity to the type of information
> > exposed under /sys/firmware/dmi/entries/...
> > 
> > This functionality is primarily intended to serve as a host->guest
> > configuration data transfer mechanism that is both:
> > 
> >         - asynchronous: the host doesn't need to wait for the guest
> >                         to be ready to accept data (e.g., by starting
> >                         an agent daemon)
> > 
> >         - out-of-band:  there is no need to commandeer a guest element
> >                         normally visible and available to the guest user
> >                         (e.g., kernel cmdline, mounting floppy/cdrom, etc.)
> > 
> > QEMU now allows arbitrary fw_cfg blobs to be added via the command line,
> > so it would be nice to make them easy to retrieve from within the guest
> > OS, and the niceset and easiest way I can think of is
> > 
> >         cat /sys/firmware/qemu-fw-cfg/.../<some-blob-name>/raw
> > 
> > New since v7:
> > 
> > 	- kbuild testbot complained about a warning on ia64, so limit
> > 	  the availability of fw_cfg in Kconfig to only architectures
> > 	  on which QEMU makes it available, which include:
> > 
> > 		(ARM || ARM64 || PPC_PMAC || SPARC || X86)
> 
> This is looking pretty good now. Does anyone have remaining
> objections before this gets merged?

All now merged in my tree, thanks.

greg k-h