Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933290AbbLSPK6 (ORCPT ); Sat, 19 Dec 2015 10:10:58 -0500 Received: from SMTP.ANDREW.CMU.EDU ([128.2.157.38]:42101 "EHLO smtp.andrew.cmu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933155AbbLSPKz (ORCPT ); Sat, 19 Dec 2015 10:10:55 -0500 Date: Sat, 19 Dec 2015 10:10:07 -0500 From: "Gabriel L. Somlo" To: Pavel Machek Cc: gregkh@linuxfoundation.org, 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, jordan.l.justen@intel.com, mst@redhat.com, peter.maydell@linaro.org, leif.lindholm@linaro.org, ard.biesheuvel@linaro.org, pbonzini@redhat.com, kraxel@redhat.com, luto@amacapital.net, stefanha@gmail.com, revol@free.fr, matt@codeblueprint.co.uk Subject: Re: [PATCH v6 0/4] SysFS driver for QEMU fw_cfg device Message-ID: <20151219151006.GA11545@GLSMBP.INI.CMU.EDU> References: <1449242946-12062-1-git-send-email-somlo@cmu.edu> <20151217160923.GI19448@HEDWIG.INI.CMU.EDU> <20151219091228.GA6024@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151219091228.GA6024@amd> X-Clacks-Overhead: GNU Terry Pratchett User-Agent: Mutt/1.5.24 (2015-08-30) X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.12.19.150016 X-SMTP-Spam-Clean: 28% ( SXL_IP_DYNAMIC 3, MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, KNOWN_FREEWEB_URI 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1700_1799 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, NO_URI_HTTPS 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, REFERENCES 0, URI_ENDS_IN_HTML 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __KNOWN_FREEWEB_URI2 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __MULTIPLE_URI_TEXT 0, __PHISH_SPEAR_STRUCTURE_1 0, __RDNS_POOLED_10 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_IN_BODY 0, __URI_NO_MAILTO 0, __URI_NS , __USER_AGENT 0) X-SMTP-Spam-Score: 28% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1970 Lines: 50 Hi Pavel, On Sat, Dec 19, 2015 at 10:12:28AM +0100, Pavel Machek wrote: > On Thu 2015-12-17 11:09:23, Gabriel L. Somlo wrote: > > ping ? > > > > Also, for the corresponding patch set on the QEMU end of things, > > ping on http://thread.gmane.org/gmane.comp.emulators.qemu/376321 > > I guess missing information is why such access is a good > idea. Debugging? Debugging did come up in earlier threads as well. However, personally, I am interested in a mechanism for the host to pass information to the guest in a way that's both - asynchronous: i.e., host doesn't need to wait for guest to be ready to accept data (e.g. by first starting an agent) - out-of-band: don't commandeer guest elements normally visible and available to guest *users* (e.g. kernel command line, mount a floppy/cdrom image, etc). QEMU now allows arbitrary fw_cfg blobs to be added via the command line, so it would be nice to make it easy to access them from the guest OS -- and what's nicer and easier than: cat /sys/firmware/qemu-fw-cfg/.../some-blob-name/raw Thanks, --Gabriel > > On Fri, Dec 04, 2015 at 10:29:02AM -0500, Gabriel L. Somlo wrote: > > > 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/... > > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/