From: Matt Fleming <matt.fleming@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
rjones@redhat.com, "Gabriel L. Somlo" <gsomlo@gmail.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] host->guest environment variables via fw_cfg
Date: Thu, 26 Feb 2015 10:55:35 +0000 [thread overview]
Message-ID: <1424948135.21588.37.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <54EEEB26.9060102@redhat.com>
On Thu, 2015-02-26 at 10:45 +0100, Laszlo Ersek wrote:
> On 02/26/15 02:13, Gabriel L. Somlo wrote:
> > For myself, I'm tempted to write a kernel driver to allow me to simply
> > "cat /sys/firmware/fw_cfg/etc/guestinfo | grep '^key_name='" when I
> > need to retrieve a guest environment variable.
>
> You might not need a kernel driver for this. If you have ioport access
> (on x86), you can speak the fwcfg "protocol" directly.
Personally, I'd be much happier to see this information exposed
via /sys/firmware/fw_cfg, not least because that allows you to use the
same tools on x86, arm64, etc.
next prev parent reply other threads:[~2015-02-26 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 19:43 [Qemu-devel] [RFC PATCH 0/2] host->guest environment variables via fw_cfg Gabriel L. Somlo
2015-02-24 19:43 ` [Qemu-devel] [RFC PATCH 1/2] fw_cfg: Add -guestenv qemu command line option Gabriel L. Somlo
2015-02-24 19:43 ` [Qemu-devel] [RFC PATCH 2/2] qga: add --getenv option to get env. vars from fw_cfg Gabriel L. Somlo
2015-02-25 9:09 ` Daniel P. Berrange
2015-02-24 23:07 ` [Qemu-devel] [RFC PATCH 0/2] host->guest environment variables via fw_cfg Laszlo Ersek
2015-02-25 22:40 ` Matt Fleming
2015-02-26 1:13 ` Gabriel L. Somlo
2015-02-26 9:45 ` Laszlo Ersek
2015-02-26 10:55 ` Matt Fleming [this message]
2015-02-26 11:13 ` Richard W.M. Jones
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=1424948135.21588.37.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=gsomlo@gmail.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).