qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org,
	Alex Williamson <alex.williamson@redhat.com>,
	Alex Graf <agraf@suse.de>,
	kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH] kernel vfio: enabled and supported on power
Date: Sun, 13 May 2012 08:29:43 +1000	[thread overview]
Message-ID: <1336861783.31450.4.camel@pasglop> (raw)
In-Reply-To: <4FAE11D1.9090103@ozlabs.ru>

On Sat, 2012-05-12 at 17:31 +1000, Alexey Kardashevskiy wrote:
> And drivers/vfio/vfio_iommu_x86.c works perfect for POWER except a DMA
> window setup
> which I dropped for now and simply use quite popular configuration on
> power (1Gb DMA window starting
> from 0x0).
> 
> As for me, it is too complicated. We do not need either
> - platform specific IOMMU chardev  or
> - IOMMU API at all
> 
> What do I miss? 

I think we want to get rid of the "generic" iommu API and make it x86
specific at this stage. A lot of what the guest is going to do with the
iommu is really platform specific at this stage, especially when we
start adding the EEH functionality, which is PE-based, or when we want
to implement the guest calls for creating dynamic windows.

Cheers,
Ben.

  reply	other threads:[~2012-05-12 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  7:31 [Qemu-devel] [RFC PATCH] kernel vfio: enabled and supported on power Alexey Kardashevskiy
2012-05-12 22:29 ` Benjamin Herrenschmidt [this message]
2012-05-14  4:04 ` 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=1336861783.31450.4.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm@vger.kernel.org \
    --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).