All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baptiste Reynal <b.reynal@virtualopensystems.com>
To: qemu-devel@nongnu.org, kvmarm@lists.cs.columbia.edu
Cc: tech@virtualopensystems.com,
	Baptiste Reynal <b.reynal@virtualopensystems.com>,
	eric.auger@linaro.org
Subject: [Qemu-devel] [RFC PATCH 0/4] VFIO platform: Use device properties API
Date: Mon, 12 Jan 2015 14:21:39 +0100	[thread overview]
Message-ID: <1421068903-8981-1-git-send-email-b.reynal@virtualopensystems.com> (raw)

This RFC shows the implementation on QEMU side of the device properties interface
presented in kernel patch series:
[RFC PATCH v3 0/3] vfio: platform: return device properties for a platform device
from branch vfio-device-properties-v3 on the repository:
https://github.com/virtualopensystems/linux-kvm-arm.git

When a VFIO device is bound to the VM, properties are queried to the host 
to fill the device tree.

One issue here is wheter a property may change between the host and the guest.
Currently, interrupt numbers and registers change, other information are kept
(including interrupt type and flags).

Regarding the clock, any primecell device requiring a clock is attached to 
apb-pclk.

DMA pl330 is used as an example. For this reason the last patch 
(3/3, arm,pl330 vfio device property) relies on the following
patch series: [RFC PATCH v2 0/3] VFIO support for AMBA devices.

Baptiste Reynal (4):
  linux-headers update
  hw/vfio/common.c : vfio_get_dev_property
  hw/arm/sysbus-fdt: vfio device property for interrupts
  hw/arm/sysbus-fdt: arm,pl330 vfio device property

 hw/arm/sysbus-fdt.c           | 134 ++++++++++++++++++++++++++++++++++++------
 hw/vfio/common.c              |  33 +++++++++++
 include/hw/vfio/vfio-common.h |   2 +
 linux-headers/linux/vfio.h    |  25 ++++++++
 4 files changed, 175 insertions(+), 19 deletions(-)

-- 
2.2.1

             reply	other threads:[~2015-01-12 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 13:21 Baptiste Reynal [this message]
2015-01-12 13:21 ` [Qemu-devel] [RFC PATCH 1/4] linux-headers update Baptiste Reynal
2015-01-12 13:21 ` [Qemu-devel] [RFC PATCH 2/4] hw/vfio/common.c : vfio_get_dev_property Baptiste Reynal
2015-01-12 15:36   ` Alex Williamson
2015-01-12 13:21 ` [Qemu-devel] [RFC PATCH 3/4] hw/arm/sysbus-fdt: vfio device property for interrupts Baptiste Reynal
2015-01-15 15:57   ` Eric Auger
2015-01-12 13:21 ` [Qemu-devel] [RFC PATCH 4/4] hw/arm/sysbus-fdt: arm, pl330 vfio device property Baptiste Reynal
2015-01-15 16:16   ` Eric Auger

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=1421068903-8981-1-git-send-email-b.reynal@virtualopensystems.com \
    --to=b.reynal@virtualopensystems.com \
    --cc=eric.auger@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=qemu-devel@nongnu.org \
    --cc=tech@virtualopensystems.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.