From mboxrd@z Thu Jan  1 00:00:00 1970
From: listmail <listmail@triad.rr.com>
Subject: Re: Re: vt-d p7p55d evo: Success
Date: Thu, 15 Apr 2010 20:57:38 -0400
Message-ID: <4BC7B602.8050609@triad.rr.com>
References: <4BB6B79D.3070305@triad.rr.com>
	<69A986FE-7EE1-48AD-9829-717094C9A49A@xs4all.nl>
	<989182286.20100405232436@eikelenboom.it>
	<201004090157.56930.mark.hurenkamp@xs4all.nl>
	<55086329-E5F1-416D-B4A5-B0C6A1B943AF@xs4all.nl>
	<4BC12DA5.9030304@triad.rr.com> <20100411111845.GI1878@reaktio.net>
	<20100411135031.GK1878@reaktio.net> <4BC219E0.5050506@triad.rr.com>
	<20100412072524.GX1878@reaktio.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20100412072524.GX1878@reaktio.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Pasi K=E4rkk=E4inen wrote:
> On Sun, Apr 11, 2010 at 02:50:08PM -0400, listmail wrote:
>  =20
>> - Xen version
>> 4.0-rc8
>>
>> - Dom0 kernel version, and if it's pvops or xenlinux based / Guest OS =
=20
>> and driver version
>> same kernel for both, via git clone of xen/stable-2.6.32 @ commit =20
>> 062aaac18de6d875fcc646359179449218f486c5
>> packaged for install via debian's make-kpkg
>> used the .config attached here: =20
>> http://lists.xensource.com/archives/html/xen-users/2010-03/msg00878.ht=
ml
>>
>> -- "lspci" output for the graphics card to get the PCI IDs and model =20
>> information
>> dom0 lspci -vv
>> <snip>
>>
>> - Did you passthru all the PCI IDs or just one?
>> I'm only aware of one ID -> xen-pciback.hide=3D(01:00.0)
>>
>>    =20
>
> Btw did you try without hiding from dom0?=20
>
> I've added your info to the wiki page now.
>
> Thanks!
>
> -- Pasi
>
>  =20
Just a small follow up

late binding
# VGA
#01:00.0 0300: 10de:0600 (rev a2)
echo "10de 0600" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:01:00.0" > /sys/bus/pci/devices/0000:01:00.0/driver/unbind
echo "0000:01:00.0" > /sys/bus/pci/drivers/pci-stub/bind

# USB
#00:1a.0 0c03: 8086:3b3c (rev 05)
echo "8086 3b3c" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1a.0" > /sys/bus/pci/devices/0000:00:1a.0/driver/unbind
echo "0000:00:1a.0" > /sys/bus/pci/drivers/pci-stub/bind

# USB
#00:1d.0 0c03: 8086:3b34 (rev 05)
echo "8086 3b34" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:00:1d.0" > /sys/bus/pci/devices/0000:00:1d.0/driver/unbind
echo "0000:00:1d.0" > /sys/bus/pci/drivers/pci-stub/bind

Results were the same.  I noticed a message:
pciback pci-1-0: 22 Couldn't locate PCI device (0000:01:00.0)! perhaps=20
already in-use?

Maybe this is because I'm doing all of this from script and immediately=20
starting the hvm.  Could use a delay?


I also patched in load BIOS from file and results were the same

The only thing *new* that I've noticed is that when power saving/screen=20
blank occurred on console, mouse/keyboard (usb controllers passed=20
through per above) movement from domU would not wake it up.  I  thought=20
perhaps it was actually coming in from setterm on dom0.  If this is the=20
case I assume setterm -blank 0 -powersave off -powerdown 0 may handle tha=
t.