From: Joerg Roedel <joerg.roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, <aik@ozlabs.ru>,
<benh@kernel.crashing.org>, <dwmw2@infradead.org>,
<chrisw@redhat.com>, <agraf@suse.de>, <scottwood@freescale.com>,
<B08248@freescale.com>, <rusty@rustcorp.com.au>,
<iommu@lists.linux-foundation.org>, <qemu-devel@nongnu.org>,
<linux-kernel@vger.kernel.org>, <joro@8bytes.org>
Subject: Re: [RFC] Device isolation infrastructure v2
Date: Fri, 16 Dec 2011 15:53:53 +0100 [thread overview]
Message-ID: <20111216145353.GA29877@amd.com> (raw)
In-Reply-To: <1323972307.2437.19.camel@x201.home>
On Thu, Dec 15, 2011 at 11:05:07AM -0700, Alex Williamson wrote:
> Starting with it in the core and hand waving some future use that we
> don't plan to implement right now seems like the wrong direction.
I agree with Alex. First of all, I havn't seen any real vfio problem
that can't be solved with the current approach, and it has the great
advantage of simplicity. It doesn't require a re-implementation of the
driver-core based on groups. I agree that we need some improvements to
Alex' code for the dma-api layer to solve the problem with broken devices
using the wrong requestor-id. But that can be done incrementally with
the current (current == in the iommu-tree) approach implemented by Alex.
I also think that all this does not belong into the driver core for two
reasons:
1) The information for building the device groups is provided
by the iommu-layer
2) The group information is provided to vfio by the iommu-api
This makes the iommu-layer the logical point to place the grouping code.
There are some sources outside of the iommu-layer that may influence
grouping (like pci-quirks), but most of the job is done by the
iommu-drivers.
Thanks,
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joerg.roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: chrisw@redhat.com, aik@ozlabs.ru, joro@8bytes.org,
rusty@rustcorp.com.au, agraf@suse.de, qemu-devel@nongnu.org,
B08248@freescale.com, iommu@lists.linux-foundation.org,
scottwood@freescale.com, dwmw2@infradead.org,
linux-kernel@vger.kernel.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC] Device isolation infrastructure v2
Date: Fri, 16 Dec 2011 15:53:53 +0100 [thread overview]
Message-ID: <20111216145353.GA29877@amd.com> (raw)
In-Reply-To: <1323972307.2437.19.camel@x201.home>
On Thu, Dec 15, 2011 at 11:05:07AM -0700, Alex Williamson wrote:
> Starting with it in the core and hand waving some future use that we
> don't plan to implement right now seems like the wrong direction.
I agree with Alex. First of all, I havn't seen any real vfio problem
that can't be solved with the current approach, and it has the great
advantage of simplicity. It doesn't require a re-implementation of the
driver-core based on groups. I agree that we need some improvements to
Alex' code for the dma-api layer to solve the problem with broken devices
using the wrong requestor-id. But that can be done incrementally with
the current (current == in the iommu-tree) approach implemented by Alex.
I also think that all this does not belong into the driver core for two
reasons:
1) The information for building the device groups is provided
by the iommu-layer
2) The group information is provided to vfio by the iommu-api
This makes the iommu-layer the logical point to place the grouping code.
There are some sources outside of the iommu-layer that may influence
grouping (like pci-quirks), but most of the job is done by the
iommu-drivers.
Thanks,
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-12-16 14:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 6:25 [RFC] Device isolation infrastructure v2 David Gibson
2011-12-15 6:25 ` [Qemu-devel] " David Gibson
2011-12-15 6:25 ` [PATCH 1/3] device_isolation: Infrastructure for managing device isolation groups David Gibson
2011-12-15 6:25 ` [Qemu-devel] " David Gibson
2011-12-15 6:25 ` [PATCH 2/3] device_isolation: Support isolation on POWER p5ioc2 bridges David Gibson
2011-12-15 6:25 ` [Qemu-devel] " David Gibson
2011-12-15 6:25 ` [PATCH 3/3] device_isolation: Support isolation on POWER p7ioc (IODA) bridges David Gibson
2011-12-15 6:25 ` [Qemu-devel] " David Gibson
2011-12-15 18:05 ` [RFC] Device isolation infrastructure v2 Alex Williamson
2011-12-15 18:05 ` [Qemu-devel] " Alex Williamson
2011-12-15 22:39 ` Alex Williamson
2011-12-15 22:39 ` [Qemu-devel] " Alex Williamson
2011-12-16 1:40 ` David Gibson
2011-12-16 1:40 ` [Qemu-devel] " David Gibson
2011-12-16 4:49 ` Alex Williamson
2011-12-16 4:49 ` [Qemu-devel] " Alex Williamson
2011-12-16 6:00 ` David Gibson
2011-12-16 6:00 ` [Qemu-devel] " David Gibson
2011-12-16 14:53 ` Joerg Roedel [this message]
2011-12-16 14:53 ` Joerg Roedel
2011-12-19 0:11 ` David Gibson
2011-12-19 0:11 ` [Qemu-devel] " David Gibson
2011-12-19 15:41 ` Joerg Roedel
2011-12-19 15:41 ` [Qemu-devel] " Joerg Roedel
2011-12-21 3:32 ` David Gibson
2011-12-21 3:32 ` David Gibson
2011-12-21 4:30 ` Alex Williamson
2011-12-21 4:30 ` Alex Williamson
2011-12-21 6:12 ` Aaron Fabbri
2011-12-21 6:12 ` Aaron Fabbri
[not found] ` <1324441837.29699.38.camel-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2012-01-25 3:13 ` David Gibson
2012-01-25 3:13 ` David Gibson
2012-01-25 3:13 ` David Gibson
2012-01-25 23:44 ` Alex Williamson
2012-01-25 23:44 ` [Qemu-devel] " Alex Williamson
2012-01-25 23:44 ` Alex Williamson
[not found] ` <1327535093.26484.190.camel-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2012-01-30 23:22 ` David Gibson
2012-01-30 23:22 ` David Gibson
2012-01-30 23:22 ` David Gibson
2011-12-21 16:46 ` Joerg Roedel
2011-12-21 16:46 ` Joerg Roedel
2011-12-19 15:46 ` David Woodhouse
2011-12-19 15:46 ` [Qemu-devel] " David Woodhouse
2011-12-19 22:31 ` David Gibson
2011-12-19 22:31 ` [Qemu-devel] " David Gibson
2011-12-19 22:56 ` David Woodhouse
2011-12-19 22:56 ` [Qemu-devel] " David Woodhouse
2011-12-20 0:25 ` David Gibson
2011-12-20 0:25 ` [Qemu-devel] " David Gibson
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=20111216145353.GA29877@amd.com \
--to=joerg.roedel@amd.com \
--cc=B08248@freescale.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=chrisw@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=scottwood@freescale.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.