qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Gabriel L. Somlo" <somlo@cmu.edu>
To: qemu-devel@nongnu.org
Cc: matt.fleming@intel.com, rjones@redhat.com,
	jordan.l.justen@intel.com, gleb@cloudius-systems.com,
	mdroth@linux.vnet.ibm.com, gsomlo@gmail.com, kraxel@redhat.com,
	pbonzini@redhat.com, lersek@redhat.com, armbru@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/5] fw-cfg: docs, cleanup, and user-provided cmdline blobs
Date: Sat, 21 Mar 2015 16:23:45 -0400	[thread overview]
Message-ID: <1426969430-14941-1-git-send-email-somlo@cmu.edu> (raw)

Document and clean up fw_cfg; additionally, allow user-provided blobs to
be inserted into fw_cfg via the qemu command line.

Changes since v2:

    - entire series depends on (applies on top of) another fw_cfg patch:
      (http://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg04278.html)
      which is currently queued for 2.3.0-rc.

    - documentation (1/5) is now correct about all architectures using
      fw_cfg revision 0x1 :)

    - patches 2/5, 3/5, and 4/5 are unchanged

    - patch 5/5 (command-line insertion of fw_cfg blob) is now using
      qemu_opts_foreach() after machine_init, and is therefore
      compliant with -writeconfig and -readconfig (thanks again Laszlo,
      Gerd, and Markus for the quick tutorial!).
      Also, ee additional comments below the commit log in the actual
      patch message.

Thanks,
  Gabriel

Gabriel L. Somlo (5):
  fw_cfg: add documentation file (docs/specs/fw_cfg.txt)
  fw_cfg: remove support for guest-side data writes
  fw_cfg: prevent selector key conflict
  fw_cfg: prohibit insertion of duplicate fw_cfg file names
  fw_cfg: insert fw_cfg file blobs via qemu cmdline

 docs/specs/fw_cfg.txt     | 226 ++++++++++++++++++++++++++++++++++++++++++++++
 hw/nvram/fw_cfg.c         |  45 ++-------
 include/hw/nvram/fw_cfg.h |   2 -
 qemu-options.hx           |  11 +++
 trace-events              |   2 -
 vl.c                      |  63 +++++++++++++
 6 files changed, 308 insertions(+), 41 deletions(-)
 create mode 100644 docs/specs/fw_cfg.txt

-- 
2.1.0

             reply	other threads:[~2015-03-21 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 20:23 Gabriel L. Somlo [this message]
2015-03-21 20:23 ` [Qemu-devel] [PATCH v3 1/5] fw_cfg: add documentation file (docs/specs/fw_cfg.txt) Gabriel L. Somlo
2015-03-23  8:26   ` Laszlo Ersek
2015-03-21 20:23 ` [Qemu-devel] [PATCH v3 2/5] fw_cfg: remove support for guest-side data writes Gabriel L. Somlo
2015-03-21 20:23 ` [Qemu-devel] [PATCH v3 3/5] fw_cfg: prevent selector key conflict Gabriel L. Somlo
2015-03-21 20:23 ` [Qemu-devel] [PATCH v3 4/5] fw_cfg: prohibit insertion of duplicate fw_cfg file names Gabriel L. Somlo
2015-03-21 20:23 ` [Qemu-devel] [PATCH v3 5/5] fw_cfg: insert fw_cfg file blobs via qemu cmdline Gabriel L. Somlo
2015-03-23  8:48   ` Laszlo Ersek
2015-03-23 13:19     ` Gabriel L. Somlo
2015-03-23 14:11       ` Laszlo Ersek
2015-03-23 15:52         ` Paolo Bonzini
2015-04-08 15:02           ` Gabriel L. Somlo
2015-04-09  8:33             ` Gerd Hoffmann

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=1426969430-14941-1-git-send-email-somlo@cmu.edu \
    --to=somlo@cmu.edu \
    --cc=armbru@redhat.com \
    --cc=gleb@cloudius-systems.com \
    --cc=gsomlo@gmail.com \
    --cc=jordan.l.justen@intel.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=matt.fleming@intel.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.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).