All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Gabriel L. Somlo" <somlo@cmu.edu>
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
Date: Sat, 19 Dec 2015 10:12:28 +0100	[thread overview]
Message-ID: <20151219091228.GA6024@amd> (raw)
In-Reply-To: <20151217160923.GI19448@HEDWIG.INI.CMU.EDU>

Hi!

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?

								Pavel

> 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

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: "Gabriel L. Somlo" <somlo@cmu.edu>
Cc: mark.rutland@arm.com, peter.maydell@linaro.org, mst@redhat.com,
	matt@codeblueprint.co.uk, stefanha@gmail.com,
	qemu-devel@nongnu.org, eric@anholt.net, kraxel@redhat.com,
	linux-api@vger.kernel.org, agross@codeaurora.org,
	pawel.moll@arm.com, zajec5@gmail.com,
	rmk+kernel@arm.linux.org.uk, lersek@redhat.com,
	devicetree@vger.kernel.org, arnd@arndb.de,
	ijc+devicetree@hellion.org.uk, jordan.l.justen@intel.com,
	galak@codeaurora.org, leif.lindholm@linaro.org,
	robh+dt@kernel.org, ard.biesheuvel@linaro.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	luto@amacapital.net, hanjun.guo@linaro.org, sudeep.holla@arm.com,
	pbonzini@redhat.com, revol@free.fr
Subject: Re: [Qemu-devel] [PATCH v6 0/4] SysFS driver for QEMU fw_cfg device
Date: Sat, 19 Dec 2015 10:12:28 +0100	[thread overview]
Message-ID: <20151219091228.GA6024@amd> (raw)
In-Reply-To: <20151217160923.GI19448@HEDWIG.INI.CMU.EDU>

Hi!

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?

								Pavel

> 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

  reply	other threads:[~2015-12-19  9:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 15:29 [PATCH v6 0/4] SysFS driver for QEMU fw_cfg device Gabriel L. Somlo
2015-12-04 15:29 ` [Qemu-devel] " Gabriel L. Somlo
2015-12-04 15:29 ` [PATCH v6 1/4] firmware: introduce sysfs driver for QEMU's " Gabriel L. Somlo
2015-12-04 15:29   ` [Qemu-devel] " Gabriel L. Somlo
2015-12-04 15:29   ` Gabriel L. Somlo
2015-12-04 15:29 ` [PATCH v6 2/4] kobject: export kset_find_obj() for module use Gabriel L. Somlo
2015-12-04 15:29   ` [Qemu-devel] " Gabriel L. Somlo
2015-12-04 15:29   ` Gabriel L. Somlo
2015-12-04 15:29 ` [PATCH v6 3/4] firmware: create directory hierarchy for sysfs fw_cfg entries Gabriel L. Somlo
2015-12-04 15:29   ` [Qemu-devel] " Gabriel L. Somlo
2015-12-04 15:29   ` Gabriel L. Somlo
2015-12-04 15:29 ` [PATCH v6 4/4] devicetree: update documentation for fw_cfg ARM bindings Gabriel L. Somlo
2015-12-04 15:29   ` [Qemu-devel] " Gabriel L. Somlo
2015-12-04 15:29   ` Gabriel L. Somlo
2015-12-17 16:09 ` [PATCH v6 0/4] SysFS driver for QEMU fw_cfg device Gabriel L. Somlo
2015-12-17 16:09   ` [Qemu-devel] " Gabriel L. Somlo
2015-12-19  9:12   ` Pavel Machek [this message]
2015-12-19  9:12     ` Pavel Machek
2015-12-19 15:10     ` Gabriel L. Somlo
2015-12-19 15:10       ` [Qemu-devel] " Gabriel L. Somlo
2015-12-19 15:10       ` Gabriel L. Somlo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151219091228.GA6024@amd \
    --to=pavel@ucw.cz \
    --cc=agross@codeaurora.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hanjun.guo@linaro.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jordan.l.justen@intel.com \
    --cc=kraxel@redhat.com \
    --cc=leif.lindholm@linaro.org \
    --cc=lersek@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mark.rutland@arm.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=mst@redhat.com \
    --cc=pawel.moll@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ralf@linux-mips.org \
    --cc=revol@free.fr \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=somlo@cmu.edu \
    --cc=stefanha@gmail.com \
    --cc=sudeep.holla@arm.com \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.