All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [TESTDAY] PV / HVM pass-through works when IOMMU present; weird failures when not
Date: Fri, 28 Jun 2013 17:13:39 +0100	[thread overview]
Message-ID: <1372436019.8976.171.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <51CDCF5302000078000E1A47@nat28.tlf.novell.com>

On Fri, 2013-06-28 at 17:00 +0100, Jan Beulich wrote:
> Also, I can't really see how the guest would be able to interact
> with a half way assigned device properly - I could imagine you
> being able to look at its config space, and perhaps load the
> driver, but I can't see an I/O to succeed, at least not as long
> as any bus mastering is being used the device (this ought to
> crash this guest, another guest, or the host, or deliver corrupt
> data). Purely port based I/O would likely work, but other than
> serial cards I can't think of many things that would do so.

That's what I was thinking. I would be useful to know what sort of
device this is and to what extent it is "working".

Ian.

  parent reply	other threads:[~2013-06-28 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 15:37 [TESTDAY] PV / HVM pass-through works when IOMMU present; weird failures when not George Dunlap
2013-06-28 16:00 ` Jan Beulich
2013-06-28 16:10   ` George Dunlap
2013-07-01 12:14     ` Jan Beulich
2013-06-28 16:13   ` Ian Campbell [this message]
2013-07-01 10:53   ` George Dunlap
2013-07-01 12:15     ` George Dunlap
2013-07-01 12:31       ` Jan Beulich
2013-07-01 13:17         ` Ian Jackson
2013-07-01 13:42           ` Jan Beulich
2013-07-01 14:15         ` Stefano Stabellini
2013-07-01 14:19         ` Ian Jackson
2013-07-01 12:26     ` Jan Beulich

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=1372436019.8976.171.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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 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.