From: Aaron Fabbri <aafabbri@cisco.com>
To: Alex Williamson <alex.williamson@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: <chrisw@redhat.com>, <aik@ozlabs.ru>, <rusty@rustcorp.com.au>,
<agraf@suse.de>, <qemu-devel@nongnu.org>, <B08248@freescale.com>,
<iommu@lists.linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
<scottwood@freescale.com>, David Woodhouse <dwmw2@infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Device isolation infrastructure v2
Date: Tue, 20 Dec 2011 22:12:45 -0800 [thread overview]
Message-ID: <CB16B8DD.149D7%aafabbri@cisco.com> (raw)
In-Reply-To: <1324441837.29699.38.camel@bling.home>
On 12/20/11 8:30 PM, "Alex Williamson" <alex.williamson@redhat.com> wrote:
> On Wed, 2011-12-21 at 14:32 +1100, David Gibson wrote:
>> On Mon, Dec 19, 2011 at 04:41:56PM +0100, Joerg Roedel wrote:
>>> On Mon, Dec 19, 2011 at 11:11:25AM +1100, David Gibson wrote:
<snip>
>>>
>>> Well, the iommu-api was designed for amd-vi and vt-d. But its concepts
>>> turn out to be more general and by no way x86-centric anymore.
>>
>> It's improving, but there are still plenty of x86isms there.
>
> Having worked on ia64 for a while, it's interesting to see this x86
> bashing from the other side. Everyone is more than willing to make
> architecture neutral interfaces (jeez, look at the extent of the vfio
> reworks), but it's not fair to throw away interfaces as x86-centric if
> you're not pushing your requirements and making use of the code.
>
> It seems like we'd be better served today to start with the vfio code we
> have and let that be the catalyst to drive an iommu api that better
> serves non-x86. I don't see how this group management tangent is really
> getting us anywhere. Thanks,
I'd agree that incremental approach here is key. VFIO has already seen a
ton of rework to accommodate all architectures. Let's not bite off a bunch
of these other subsystem rewrites in the same chunk as our VFIO effort.
-Aaron
WARNING: multiple messages have this Message-ID (diff)
From: Aaron Fabbri <aafabbri@cisco.com>
To: Alex Williamson <alex.williamson@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: chrisw@redhat.com, aik@ozlabs.ru, rusty@rustcorp.com.au,
agraf@suse.de, qemu-devel@nongnu.org, B08248@freescale.com,
iommu@lists.linux-foundation.org, scottwood@freescale.com,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC] Device isolation infrastructure v2
Date: Tue, 20 Dec 2011 22:12:45 -0800 [thread overview]
Message-ID: <CB16B8DD.149D7%aafabbri@cisco.com> (raw)
In-Reply-To: <1324441837.29699.38.camel@bling.home>
On 12/20/11 8:30 PM, "Alex Williamson" <alex.williamson@redhat.com> wrote:
> On Wed, 2011-12-21 at 14:32 +1100, David Gibson wrote:
>> On Mon, Dec 19, 2011 at 04:41:56PM +0100, Joerg Roedel wrote:
>>> On Mon, Dec 19, 2011 at 11:11:25AM +1100, David Gibson wrote:
<snip>
>>>
>>> Well, the iommu-api was designed for amd-vi and vt-d. But its concepts
>>> turn out to be more general and by no way x86-centric anymore.
>>
>> It's improving, but there are still plenty of x86isms there.
>
> Having worked on ia64 for a while, it's interesting to see this x86
> bashing from the other side. Everyone is more than willing to make
> architecture neutral interfaces (jeez, look at the extent of the vfio
> reworks), but it's not fair to throw away interfaces as x86-centric if
> you're not pushing your requirements and making use of the code.
>
> It seems like we'd be better served today to start with the vfio code we
> have and let that be the catalyst to drive an iommu api that better
> serves non-x86. I don't see how this group management tangent is really
> getting us anywhere. Thanks,
I'd agree that incremental approach here is key. VFIO has already seen a
ton of rework to accommodate all architectures. Let's not bite off a bunch
of these other subsystem rewrites in the same chunk as our VFIO effort.
-Aaron
next prev parent reply other threads:[~2011-12-21 6:22 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
2011-12-16 14:53 ` [Qemu-devel] " 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 [this message]
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=CB16B8DD.149D7%aafabbri@cisco.com \
--to=aafabbri@cisco.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=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.