qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL] VirtFS update 6
Date: Sat, 15 Oct 2011 15:49:10 +0530	[thread overview]
Message-ID: <874nza8sm9.fsf@linux.vnet.ibm.com> (raw)


The following changes since commit ebffe2afceb1a17b5d134b5debf553955fe5ea1a:

  Merge remote-tracking branch 'qmp/queue/qmp' into staging (2011-10-10 08:21:46 -0500)

are available in the git repository at:

  git://repo.or.cz/qemu/v9fs.git for-upstream-6

Aneesh Kumar K.V (7):
      hw/9pfs: Use ioeventfd for 9p
      hw/9pfs: Add new virtfs option writeout=immediate skip host page cache
      qemu-options.hx: Update virtfs command documentation
      hw/9pfs: Fix build error on platform that don't support futimens
      hw/9pfs: Use export_flag for indicating whether fs driver use path names.
      hw/9pfs: Rename fstype to fsdriver to make it consistent across VirtFS code
      hw/9pfs: Use export flag for indicating security model

Daniel P. Berrange (1):
      hw/9pfs: Ensure an error is reported to user if 9pfs mount tag is too long

Harsh Prateek Bora (5):
      hw/9pfs: Add st_gen support in getattr reply
      hw/9pfs: Add st_gen support for handle based fs driver
      hw/9pfs: Introduce tracing for 9p pdu handlers
      hw/9pfs: Remove virtio-9p-debug.* infra to be replaced by Qemu Tracing.
      scripts: Simpletrace log analysis script for pretty-printing 9p log.

M. Mohan Kumar (4):
      virtio-9p: Use 9P specific Lock constants
      hw/9pfs: Add open flag mapping
      hw/9pfs: Use fs driver specific lstat
      hw/9pfs: Handle Security model parsing

 Makefile.objs                     |    2 +-
 configure                         |   33 ++
 fsdev/file-op-9p.h                |   51 ++--
 fsdev/qemu-fsdev.c                |   69 +++--
 fsdev/qemu-fsdev.h                |   20 +-
 hw/9pfs/cofile.c                  |   24 ++
 hw/9pfs/cofs.c                    |    2 +-
 hw/9pfs/virtio-9p-coth.h          |    3 +
 hw/9pfs/virtio-9p-debug.c         |  646 -------------------------------------
 hw/9pfs/virtio-9p-debug.h         |    6 -
 hw/9pfs/virtio-9p-device.c        |   70 ++--
 hw/9pfs/virtio-9p-handle.c        |  120 +++++--
 hw/9pfs/virtio-9p-local.c         |  126 ++++++--
 hw/9pfs/virtio-9p.c               |  170 +++++++++-
 hw/9pfs/virtio-9p.h               |   35 ++-
 hw/virtio-pci.c                   |    5 -
 hw/virtio-pci.h                   |    5 +
 qemu-config.c                     |   14 +-
 qemu-options.hx                   |  122 +++++---
 scripts/analyse-9p-simpletrace.py |  142 ++++++++
 trace-events                      |   46 +++
 vl.c                              |   24 +-
 22 files changed, 852 insertions(+), 883 deletions(-)
 delete mode 100644 hw/9pfs/virtio-9p-debug.c
 delete mode 100644 hw/9pfs/virtio-9p-debug.h
 create mode 100755 scripts/analyse-9p-simpletrace.py

             reply	other threads:[~2011-10-15 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15 10:19 Aneesh Kumar K.V [this message]
2011-10-20 15:01 ` [Qemu-devel] [PULL] VirtFS update 6 Anthony Liguori

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=874nza8sm9.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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).