From: Alexander Graf <agraf@suse.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: chrisw@sous-sol.org, aik@au1.ibm.com, pmac@au1.ibm.com,
dwg@au1.ibm.com, joerg.roedel@amd.com, benve@cisco.com,
aafabbri@cisco.com, B08248@freescale.com, B07421@freescale.com,
avi@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] VFIO-NG group/device/iommu framework
Date: Wed, 7 Sep 2011 13:58:14 +0200 [thread overview]
Message-ID: <3B2BACC2-C445-4F32-8E21-19FD28FF2CDC@suse.de> (raw)
In-Reply-To: <20110901194915.2391.97400.stgit@s20.home>
On 01.09.2011, at 21:50, Alex Williamson wrote:
> Trying to move beyond talking about how VFIO should work to
> re-writing the code. This is pre-alpha, known broken, will
> probably crash your system but it illustrates some of how
> I see groups, devices, and iommus interacting. This is just
> the framework, no code to actually support user space drivers
> or device assignment yet.
>
> The iommu portions are still using the "FIXME" PCI specific
> hooks. Once Joerg gets some buy-in on his bus specific iommu
> patches, we can move to that.
>
> The group management is more complicated than I'd like and
> you can get groups into a bad state by killing the test program
> with devices/iommus open. The locking is overly simplistic.
> But, it's a start. Please make constructive comments and
> suggestions. Patches based on v3.0. Thanks,
Looks pretty reasonable to me so far, but I guess we only know for sure once we have non-PCI implemented and working with this scheme as well.
Btw I couldn't find the PCI BAR regions mmaps and general config space exposure. Where has that gone?
Alex
next prev parent reply other threads:[~2011-09-07 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110901194915.2391.97400.stgit@s20.home>
2011-09-01 19:50 ` [RFC PATCH 1/5] iommu: Add iommu_device_group callback and iommu_group sysfs entry Alex Williamson
2011-09-01 19:50 ` [RFC PATCH 2/5] intel-iommu: Implement iommu_device_group Alex Williamson
2011-09-01 19:50 ` [RFC PATCH 3/5] VFIO: Base framework for new VFIO driver Alex Williamson
2011-09-01 19:50 ` [RFC PATCH 4/5] VFIO: Add PCI device support Alex Williamson
2011-09-01 19:50 ` [RFC PATCH 5/5] VFIO: Simple test tool Alex Williamson
2011-09-07 11:58 ` Alexander Graf [this message]
2011-09-08 21:54 ` [RFC PATCH 0/5] VFIO-NG group/device/iommu framework Alex Williamson
[not found] ` <20110901195043.2391.31843.stgit@s20.home>
2011-09-07 14:52 ` [RFC PATCH 3/5] VFIO: Base framework for new VFIO driver Konrad Rzeszutek Wilk
2011-09-19 16:42 ` Alex Williamson
[not found] ` <20110901195050.2391.12028.stgit@s20.home>
2011-09-07 18:55 ` [RFC PATCH 4/5] VFIO: Add PCI device support Konrad Rzeszutek Wilk
2011-09-08 7:52 ` Avi Kivity
2011-09-08 21:52 ` Alex Williamson
2011-09-01 19:50 [RFC PATCH 0/5] VFIO-NG group/device/iommu framework Alex Williamson
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=3B2BACC2-C445-4F32-8E21-19FD28FF2CDC@suse.de \
--to=agraf@suse.de \
--cc=B07421@freescale.com \
--cc=B08248@freescale.com \
--cc=aafabbri@cisco.com \
--cc=aik@au1.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=benve@cisco.com \
--cc=chrisw@sous-sol.org \
--cc=dwg@au1.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pmac@au1.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).