All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oliver Linden <oliver_linden@helimail.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Your Kernel 3.0 git and pci passthrough
Date: Sun, 14 Aug 2011 16:41:29 -0400	[thread overview]
Message-ID: <20110814204129.GA13223@dumpdata.com> (raw)
In-Reply-To: <20110814200549.GA15827@dumpdata.com>

On Sun, Aug 14, 2011 at 04:05:49PM -0400, Konrad Rzeszutek Wilk wrote:
> On Sun, Aug 14, 2011 at 05:16:48PM +0200, Oliver Linden wrote:
> > Hello Konrad,
> > 
> > I have a similar problem as described by Sander Eikelenboom on June 21st.
> 
> Argh. Please CC xen-devel on these type of emails.
> > 
> > I compiled a kernel using your current xen.git on git.kernel.org. Even
> > with your patch - tested by Sander - is applied I'm getting the message
> > that pcistub doesn't own the pci device.
> > 
> > Checking that via lspci shows that no of the excluded devices is bound
> > to pciback.
> 
> And pciback is built in ("=y")?
> 
> > 
> > I tested the xen-pciback.hide as well as the pciback.hide parameter via
> > the commandline.
> > 
> > Is there any kernel 3 version available that supports pci-passthrough?
> 
> Well the #master which you are using , and the 3.1 that is in linus/master
> 
> > 
> > Any help is really appreciated.
> 
> Hm, let me double check, but I am not seeing the issues you guys are reporting.

Ah, I am now.

  reply	other threads:[~2011-08-14 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E47E6E0.3090403@helimail.de>
2011-08-14 20:05 ` Your Kernel 3.0 git and pci passthrough Konrad Rzeszutek Wilk
2011-08-14 20:41   ` Konrad Rzeszutek Wilk [this message]
2011-08-15 13:09     ` Konrad Rzeszutek Wilk

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=20110814204129.GA13223@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=oliver_linden@helimail.de \
    --cc=xen-devel@lists.xensource.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.