From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pciback doesn't seize device, but no error either.
Date: Mon, 15 Feb 2010 09:10:49 -0500 [thread overview]
Message-ID: <20100215141049.GA15257@phenom.dumpdata.com> (raw)
In-Reply-To: <1034474768.20100214134538@eikelenboom.it>
On Sun, Feb 14, 2010 at 01:45:38PM +0100, Sander Eikelenboom wrote:
> Hi Konrad,
>
> I'm trying to passthrough a secondary gfx device(intel IGD) (with patches from Han Weidong).
> Intel VT-D is enabled, pciback + pciback debug compiled in.
> But some how pciback refuses to seize the device, but i don't see an error either.
>
> Attached:
> - xm info
> - xm dmesg
> - dmesg
> - lspci -vvvknn
>
> Any ideas on what it might be ?
>
> --
> Best regards,
> Sander mailto:linux@eikelenboom.it
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Linux version 2.6.31.6 (root@xentest) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #2 SMP Sun Feb 14 05:18:49 CET 2010
> [ 0.000000] Command line: root=/dev/sda1 ro earlyprintk=xen pciback.hide=(0000:00:02.0)(0000:00:02.1) reassigndev=0000:00:02.0,0000:00:02.1 reassign_resources
It is called 'xen-pciback' now. Try that instead of 'pciback'.
Also, 'reassigneddev' and 'reassign_resources' are no more in the upstream
kernels. It is one single option and it is: 'pci=resource_alignment=08:02.0'.
prev parent reply other threads:[~2010-02-15 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 12:45 pciback doesn't seize device, but no error either Sander Eikelenboom
2010-02-14 14:37 ` pciback doesn't seize device, but no error either. (solved, forgot to rename to xen-pciback.hide) Sander Eikelenboom
2010-02-14 14:41 ` pciback doesn't seize device, but no error either Ervin Novak
2010-02-14 14:42 ` Ervin Novak
2010-02-15 14:10 ` Konrad Rzeszutek Wilk [this message]
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=20100215141049.GA15257@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--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.