All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org
Subject: Re: [PATCH] Enable non page boundary BAR device assignment
Date: Thu, 10 Dec 2009 13:37:07 +0200	[thread overview]
Message-ID: <20091210113707.GA12392@redhat.com> (raw)
In-Reply-To: <20091210112849.GH10800@il.ibm.com>

On Thu, Dec 10, 2009 at 01:28:49PM +0200, Muli Ben-Yehuda wrote:
> On Thu, Dec 10, 2009 at 12:56:56PM +0200, Michael S. Tsirkin wrote:
> 
> > > mmio and pio are easy, DMA you'd need an IOMMU for security, or
> > > whatever uio does just for translation,
> > 
> > uio currently does not support DMA, but I plan to fix this
> 
> With or without an IOMMU?

With an IOMMU.

> > > and interrupts you probably get for free from uio. Seems eminently
> > > doable to me. Why you'd want to is another matter :-)
> > 
> > The list above ignores the biggest issue: you would have to change
> > TCG code generation to make this work.
> 
> Yep, I know nothing about TCG, only looking at this from the device
> interaction side.
> 
> > I am not sure this problem is solvable unless host and guest
> > architectures are very similar.
> 
> Now you are ignoring the most interesting issue, namely, why would you
> want to solve it? What is the value of device assignment for TCG
> targets?

No idea.

> Cheers,
> Muli
> -- 
> Muli Ben-Yehuda | muli@il.ibm.com | +972-4-8281080
> Manager, Virtualization and Systems Architecture
> Master Inventor, IBM Research -- Haifa
> Second Workshop on I/O Virtualization (WIOV '10):
> http://sysrun.haifa.il.ibm.com/hrl/wiov2010/

  parent reply	other threads:[~2009-12-10 11:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 17:38 [PATCH] Enable non page boundary BAR device assignment Alexander Graf
2009-12-09 20:49 ` Michael S. Tsirkin
2009-12-09 21:06   ` Alexander Graf
2009-12-10 10:35     ` Avi Kivity
2009-12-10  5:16 ` Muli Ben-Yehuda
2009-12-10  9:35   ` Alexander Graf
2009-12-10 10:21     ` Muli Ben-Yehuda
2009-12-10  9:43   ` Michael S. Tsirkin
2009-12-10  9:52     ` Alexander Graf
2009-12-10 10:08       ` Alexander Graf
2009-12-10 10:27         ` Michael S. Tsirkin
2009-12-10 10:31           ` Alexander Graf
2009-12-10 10:42             ` Michael S. Tsirkin
2009-12-10 10:23       ` Muli Ben-Yehuda
2009-12-10 10:31         ` Alexander Graf
2009-12-10 10:37           ` Muli Ben-Yehuda
2009-12-10 10:56             ` Michael S. Tsirkin
2009-12-10 11:09               ` Alexander Graf
2009-12-10 11:21                 ` Michael S. Tsirkin
2009-12-10 12:12                   ` Gleb Natapov
2009-12-10 11:28               ` Muli Ben-Yehuda
2009-12-10 11:34                 ` Alexander Graf
2009-12-10 11:46                   ` Michael S. Tsirkin
2009-12-10 11:37                 ` Michael S. Tsirkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-10 23:06 Alexander Graf
2009-12-11 11:05 ` Michael S. Tsirkin
2009-12-15 18:16   ` Alexander Graf
2009-12-15 18:20     ` Michael S. Tsirkin
2009-12-15 18:24       ` Alexander Graf
2009-12-16 20:12         ` Muli Ben-Yehuda

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=20091210113707.GA12392@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=muli@il.ibm.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.