From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Baptiste Favre Subject: Re: PCI passthrough issue Date: Fri, 28 Jan 2011 16:47:44 +0100 Message-ID: <4D42E520.9020107@jbfavre.org> References: <4D2E28C5.30203@jbfavre.org> <4D2EE1DE.5070006@jbfavre.org> <4D2F5009.2090701@jbfavre.org> <20110113201922.GA20494@dumpdata.com> <4D2F6431.8030606@jbfavre.org> <20110114145350.GB7371@dumpdata.com> <4D30DC5A.9080303@jbfavre.org> <4D340504.7020203@jbfavre.org> <4D344AF4.80301@jbfavre.org> <4D3AB003.3040603@jbfavre.org> <20110127202755.GA4194@dumpdata.com> <4D41E7EE.4060502@jbfavre.org> Reply-To: xen-devel@lists.xensource.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4D41E7EE.4060502@jbfavre.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hello, I made some more tests today, still with 2.6.37 32bits kernel from Debian experimental, with various memory allocation value. For each test, I make ping on my gateway with various packet size: ping -s15 10.0.0.1 ping -s85 10.0.0.1 ping -s86 10.0.0.1 ping -s150 10.0.0.1 Results bellow: - less than 256mb: works - between 256 and 512mb: ping greater than 85 bytes does not work - more than 512mb: works I'm lost... Regards, JB Le 27/01/2011 22:47, Jean Baptiste Favre a =E9crit : > Hello Konrad, >=20 > Le 27/01/2011 21:27, Konrad Rzeszutek Wilk a =E9crit : >> On Sat, Jan 22, 2011 at 11:22:59AM +0100, Jean Baptiste Favre wrote: >>> Hello, >>> Last investigations show that I've the latest BIOS version for my >>> motherboard. >>> Do you need more tests, if yes which ones ? >> >> I tried it on my 2.6.32.27 (32-bit and 64-bit) and I am not seeing >> the failures you have. These are the devices I passed in: >> >> 00:00.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHC= I Controller #1 (rev 02) >> 00:00.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHC= I Controller #2 (rev 02) >> 00:00.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHC= I Controller #3 (rev 02) >> 00:00.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EH= CI Controller #1 (rev 02) >> 00:01.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network= Connection (rev 02) >> 00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI= -X Fusion-MPT Dual Ultra320 SCSI (rev 07) >> 00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI= -X Fusion-MPT Dual Ultra320 SCSI (rev 07) >> 00:03.0 Ethernet controller: Intel Corporation 82572EI Gigabit Etherne= t Controller (Copper) (rev 06) >> >> Granted the kernel I am using a jeremy/xen/stable-2.6.32.x so not sure >> how divergent from Debian or Debian Squeeze it is. >> >> How are you launching your guest? Do you something like this: >> >> kernel=3D"/mnt/lab/2.6.32.27/vmlinuz" >> ramdisk=3D"/mnt/lab/2.6.32.27/initramfs.cpio.gz" >> extra=3D"console=3Dhvc0 debug test=3Dcrashme iommu=3Dsoft" >> memory=3D1024 >> maxmem=3D2048 >> vcpus=3D4 >> on_crash=3D"preserve" >> pci=3D ["00:1d.0","00:1d.1","00:1d.2","00:1d.7","0a:00.1","0000:06:01.= 1","0000:06:01.0", "09:00.0"] >> vif =3D [ 'mac=3D00:0f:4b:00:00:68, bridge=3Dswitch' ] >=20 > Here is my domU config file: > #################### > kernel =3D '/cluster/kernels/vmlinuz-2.6.37-trunk-686-bigmem' > ramdisk =3D '/cluster/kernels/initrd.img-2.6.37-trunk-686-bigmem' > builder =3D 'linux' >=20 > memory =3D '256' > memory =3D '512' > vcpus =3D '1' > cpus =3D '2' > localtime =3D 0 > serial =3D 'pty' >=20 > disk =3D [ 'drbd:xps-106,xvda,w' ] >=20 > on_poweroff =3D 'destroy' > on_reboot =3D 'restart' > on_crash =3D 'restart' >=20 > extra =3D "root=3D/dev/mapper/xps--106-root ro iommu=3Dsoft swiotlb=3Df= orce > console=3Dhvc0 xencons=3Dtty" >=20 > pci =3D [ '04:00.0' ] >=20 > name =3D 'xps-106' > hostname =3D 'xps-106.clichy.jbfavre.org' > #################### >=20 > As I privately told you, I made the tests you suggested and the result > is that problem occurs with 256mb of memory, but is solved with 512mb o= r > more. >=20 > Basically, what I find surprising is that with 256mb of memory, the max > size for incoming packets to be blocked is 128 bytes. > Makes me think about an unsigned integer or something like that, but I > don't have enough kernel knowledge to be more precise. >=20 > Regards, > JB >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20