From owner-freebsd-emulation@FreeBSD.ORG Sun Dec 23 10:33:43 2012 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5FB6939; Sun, 23 Dec 2012 10:33:43 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D9F598FC0C; Sun, 23 Dec 2012 10:33:42 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA23619; Sun, 23 Dec 2012 12:33:40 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TmisF-000FQd-Sq; Sun, 23 Dec 2012 12:33:39 +0200 Message-ID: <50D6DE03.50707@FreeBSD.org> Date: Sun, 23 Dec 2012 12:33:39 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: incorrect usage of callout_reset in vbox 4.2.4 ? References: <50C9D369.6040204@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-emulation@FreeBSD.org, vbox@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2012 10:33:43 -0000 on 20/12/2012 13:14 Bernhard Fröhlich said the following: > On Thu, Dec 13, 2012 at 2:08 PM, Andriy Gapon wrote: >> >> It looks like in timer-r0drv-freebsd.c the code tries to pass absolute time as a >> timeout parameter to callout_reset while that function actually expects relative >> time (period). >> >> I am testing the following patch, but I am sure that the code can be made more >> efficient. >> >> --- timer-r0drv-freebsd.c.orig 2012-12-12 20:13:27.623202784 +0200 >> +++ timer-r0drv-freebsd.c 2012-12-12 20:19:43.368202795 +0200 >> @@ -172,15 +172,16 @@ >> /* >> * Calc when it should start firing. >> */ >> - u64First += RTTimeNanoTS(); >> + const uint64_t u64Now = RTTimeNanoTS(); >> + u64First += u64Now; >> >> pTimer->fSuspended = false; >> pTimer->iTick = 0; >> pTimer->u64StartTS = u64First; >> pTimer->u64NextTS = u64First; >> >> - tv.tv_sec = u64First / 1000000000; >> - tv.tv_usec = (u64First % 1000000000) / 1000; >> + tv.tv_sec = (u64First - u64Now) / 1000000000; >> + tv.tv_usec = ((u64First - u64Now) % 1000000000) / 1000; >> callout_reset(&pTimer->Callout, tvtohz(&tv), rtTimerFreeBSDCallback, pTimer); >> >> return VINF_SUCCESS; >> @@ -247,8 +248,8 @@ >> if (pTimer->u64NextTS < u64NanoTS) >> pTimer->u64NextTS = u64NanoTS + RTTimerGetSystemGranularity() / 2; >> >> - tv.tv_sec = pTimer->u64NextTS / 1000000000; >> - tv.tv_usec = (pTimer->u64NextTS % 1000000000) / 1000; >> + tv.tv_sec = (pTimer->u64NextTS - u64NanoTS) / 1000000000; >> + tv.tv_usec = ((pTimer->u64NextTS - u64NanoTS) % 1000000000) / 1000; >> callout_reset(&pTimer->Callout, tvtohz(&tv), rtTimerFreeBSDCallback, pTimer); >> } > > What is your results from that tests? Is the patch correct so should we include > it into the port? I believe that the patch is correct. I haven't seen any regressions nor any visible improvements from it. -- Andriy Gapon From owner-freebsd-emulation@FreeBSD.ORG Mon Dec 24 08:59:00 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CC90D4B; Mon, 24 Dec 2012 08:59:00 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by mx1.freebsd.org (Postfix) with ESMTP id D256D8FC17; Mon, 24 Dec 2012 08:58:59 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id t11so3190348wey.12 for ; Mon, 24 Dec 2012 00:58:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:user-agent:mime-version :content-type:content-transfer-encoding:message-id; bh=1brmVYWfWVF39hQRVyh0XssWxNHoV5FyVu+qk5MMohs=; b=Bom1tE/g9F1pOJb9oQLIHLg02aI/3B4JfqjJQJgnZPOzi1L6twmFDi4o8sm+tHQVlk SV46FSiv+qrfle/XXjRxWk12HkQ7LEe9Q/wKDBGi4yMi7kesmCoEVWitIi+BaFRpiRlj tWXBd0ZwP6CRK27cDxW9K4kkgbx2a8KM91jCy9hqyS/cEG2MVl3EKvFyN1HkhBndDPeg 5gDbyBt0kq24pILCXwg/QNBBl/9DmeQ+S1qyt6HjmNFeSFF5s8d1SGn2s5f6RxWfp+WO Z3K2QcKHmzfhkQdyyhkZHrgav7x4brIvmEHGE8bduuvF0QCgoUQa9zxz16+Ht9USNB5G MtoQ== X-Received: by 10.180.24.133 with SMTP id u5mr25714890wif.17.1356339538461; Mon, 24 Dec 2012 00:58:58 -0800 (PST) Received: from dragon.dg (41-132-132-229.dsl.mweb.co.za. [41.132.132.229]) by mx.google.com with ESMTPS id bd6sm10821162wib.10.2012.12.24.00.58.55 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Dec 2012 00:58:57 -0800 (PST) From: David Naylor To: freebsd-questions@freebsd.org, freebsd-emulation@freebsd.org Subject: Wine-fbsd64 updated to 1.5.19 (32bit Wine for 64bit FreeBSD) Date: Mon, 24 Dec 2012 10:58:48 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.9.1; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1899030.dzI2tkV8WP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201212241058.51978.naylor.b.david@gmail.com> X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 08:59:00 -0000 --nextPart1899030.dzI2tkV8WP Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Packages [1] for wine-fbsd64-1.5.19 have been uploaded to mediafire [2]. T= he=20 packages for FreeBSD 10 use the pkgng [3] format. =20 Please read the installation messages, if you use the nVidia graphics drive= r,=20 for further information. =20 =46AQ =2D-- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able= to=20 isolate where the problem is occurring (wine, ports, world, kernel, i386,=20 amd64). A possible solution in to try upgrading, or downgrading, software= =20 used however I have not been able to fix the problem with my attempts. If = you=20 find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefin= ed symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with=20 wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). =20 Apologies for the inconvenience. =20 Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pk= gng=20 packages for FreeBSD-9. Since it is possible to install the existing pkg=20 packages in a pkgng environment (which I do) this is not a high priority. = =20 Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-b= yte=20 boundary. To fix, recompile world after ensuring your sources include=20 http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. =20 Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.19,1.tbz) =3D=20 c442808517aa6d77bb3c3d86f5a4031e MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.19.1.txz) =3D=20 86b2d231caba230d1829db1c961ed38c MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.19,1.txz) =3D=20 90b9aa6cc54024349ea5389efb7f9d4c [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng --nextPart1899030.dzI2tkV8WP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlDYGUsACgkQUaaFgP9pFrKC5ACfQgy6IegZT/kl5x4IiwnXhmrP mKkAoIzKolRW4LzuvCQtQxOevqvlqI4k =snRX -----END PGP SIGNATURE----- --nextPart1899030.dzI2tkV8WP-- From owner-freebsd-emulation@FreeBSD.ORG Mon Dec 24 10:28:00 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C39BD1E; Mon, 24 Dec 2012 10:28:00 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) by mx1.freebsd.org (Postfix) with ESMTP id 88CC78FC12; Mon, 24 Dec 2012 10:27:59 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id dq12so3097696wgb.0 for ; Mon, 24 Dec 2012 02:27:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:user-agent:mime-version :content-type:content-transfer-encoding:message-id; bh=/NWippv+AfssOnhP4T6BRguyOLzbLT74a0GZsUKjE1o=; b=LT/JrKHV+cEGYQOy5jdZG00WKWKg9aFQxwnZVPZP2fA4FwMnN81oMQZ5I8PUef+Yx1 yjhtm7/MRbN5k+2hu2l8s/5N9NMZOuov3DtBVA/s9RAiL+RDCqWTt6TRmLTh98+QuhRt zHPLAJkS7XeFXja6DhuxK6ZVH2d2GPZb/qvZgDPKrF27kEqor7g/B64PgnJ5dVu9Z0Rg 09Jmx2Rfj14bq6tk4Xszmu3YbpCShw2cM50KxIQ082wInUHMWc5uJ/ZCvE7yY46gUOL5 ykqtpliscmxRrW560KQfPZQO8NlxuHvyAMkZyx14kXYYbKm8sPHfYmTtO3SwFEz2bC9n LSAA== X-Received: by 10.194.71.140 with SMTP id v12mr34802447wju.36.1356344878155; Mon, 24 Dec 2012 02:27:58 -0800 (PST) Received: from dragon.dg (41-132-132-229.dsl.mweb.co.za. [41.132.132.229]) by mx.google.com with ESMTPS id ew4sm32495570wid.11.2012.12.24.02.27.55 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Dec 2012 02:27:57 -0800 (PST) From: David Naylor To: freebsd-questions@freebsd.org, freebsd-emulation@freebsd.org Subject: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD) Date: Mon, 24 Dec 2012 12:27:11 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.9.1; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1561069.onBiTI3zvH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201212241227.15165.naylor.b.david@gmail.com> X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 10:28:00 -0000 --nextPart1561069.onBiTI3zvH Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Packages [1] for wine-fbsd64-1.5.20 have been uploaded to mediafire [2]. T= he=20 packages for FreeBSD 10 use the pkgng [3] format. =20 Please read the installation messages, if you use the nVidia graphics drive= r,=20 for further information. =20 =46AQ =2D-- Q: Wine crashing when launching some 3D programs (aka games) A: This appears to be some clash with software however I have not been able= to=20 isolate where the problem is occurring (wine, ports, world, kernel, i386,=20 amd64). A possible solution in to try upgrading, or downgrading, software= =20 used however I have not been able to fix the problem with my attempts. If = you=20 find a solution please email me, or post the solution on the mailing list. Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefin= ed symbol "_ThreadRuneLocale" A: This problem is specific to FreeBSD-9.0, please either stick with=20 wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). =20 Apologies for the inconvenience. =20 Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pk= gng=20 packages for FreeBSD-9. Since it is possible to install the existing pkg=20 packages in a pkgng environment (which I do) this is not a high priority. = =20 Q: Wine doesn't run (properly) with a clang built world A: Clang was compiling i386 on a 16-byte boundary while gcc was using a 4-b= yte=20 boundary. To fix, recompile world after ensuring your sources include=20 http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant MFC. =20 Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.20,1.tbz) =3D=20 f292068a82cec3d068ce0ca6d154037c MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.20.1.txz) =3D=20 5467ea90a1ceac62f28eb4658cb53960 MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.20,1.txz) =3D=20 6961696e9c8195b2969a46ee7ffa8a21 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng --nextPart1561069.onBiTI3zvH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlDYLgMACgkQUaaFgP9pFrKm7QCdH/MqcnlLOs6CQDwXsW/CnV4r OsUAn1SqkfxP9YP49hNDdAu1sWkkrKnU =tn3k -----END PGP SIGNATURE----- --nextPart1561069.onBiTI3zvH-- From owner-freebsd-emulation@FreeBSD.ORG Mon Dec 24 11:06:41 2012 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACCC55F0 for ; Mon, 24 Dec 2012 11:06:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE908FC1E for ; Mon, 24 Dec 2012 11:06:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qBOB6f2k066001 for ; Mon, 24 Dec 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qBOB6fIv065999 for freebsd-emulation@FreeBSD.org; Mon, 24 Dec 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Dec 2012 11:06:41 GMT Message-Id: <201212241106.qBOB6fIv065999@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-emulation@FreeBSD.org Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 11:06:41 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/169988 emulation [PATCH] Update sysutils/linux-procps to 3.2.7; also up o ports/169896 emulation [patch] audio/linux-f10-alsa-lib: use OSS plugin by de o kern/169814 emulation [linux] ptrace is broken in Linux emulation o kern/169805 emulation [linux] utime() syscall does not work in linuxulator o kern/159646 emulation [linux] [patch] bump Linux version in linuxulator f kern/156691 emulation [vmware] [panic] panic when using hard disks as RAW de o kern/156353 emulation [ibcs2] ibcs2 binaries that execute on 4.x not working o kern/155577 emulation [boot] BTX halted after install. Reboot during install o kern/155040 emulation [linux] [patch] Linux recvfrom doesn't handle proto fa o kern/153990 emulation [hyper-v]: Will not install into Hyper-V on Server 200 o kern/153887 emulation [linux] Linux emulator not understand STB_GNU_UNIQUE b o kern/153243 emulation [ibcs2] Seg fault whne running COFF binary using iBCS2 o kern/151714 emulation [linux] print/acroread9 not usable due to lack of supp a bin/150262 emulation [patch] truss(1) -f doesn't follow descendants of the a kern/150186 emulation [parallels] [panic] Parallels Desktop: CDROM disconnec o ports/148097 emulation [patch] suggested addition to linux_base-* packages to o ports/148096 emulation emulators/linux_base-* can not be built from ports on o kern/147793 emulation [vmware] [panic] cdrom handling, panic, possible race o kern/146237 emulation [linux] Linux binaries not reading directories mounted p kern/144584 emulation [linprocfs][patch] bogus values in linprocfs o ports/142837 emulation [patch] emulators/linux_base-* packages fails to insta o kern/140156 emulation [linux] cdparanoia fails to read drive data f kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage s kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/86619 emulation [linux] linux emulator interacts oddly with cp a kern/72920 emulation [linux] path "prefixing" is not done on unix domain so o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/36952 emulation [patch] [linux] ldd(1) command of linux does not work o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 33 problems total. From owner-freebsd-emulation@FreeBSD.ORG Mon Dec 24 15:51:27 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 695A0587; Mon, 24 Dec 2012 15:51:27 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-f173.google.com (mail-we0-f173.google.com [74.125.82.173]) by mx1.freebsd.org (Postfix) with ESMTP id C068F8FC0C; Mon, 24 Dec 2012 15:51:26 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id z2so3245646wey.4 for ; Mon, 24 Dec 2012 07:51:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=S4wMx2EIwW19h3I5MOe8vnUmgQSOIelSOO8agr38NFM=; b=Sayx9Wb4FbJtXyX+xaSMlTutVUhKvcBi5ya7et72yXgzv1ecOf20+adwbpUZzWrClS NR0Wl9NeUxH70u95VgGiYaYLvyWuURsEvWdJUUlOblbSt7tSVaKeWAB1FsaIVTnSbWZA MtSS/USv6HO25P+yVNmJ6ol2cDuG7JU5NRE7Lz1s88E2Liomse3BIus7EAXkWGNnIdsy Sv21E5+ADqvD867KqM+6APNXBuK5wgZwH9x4WOEdLmVbroztjBuHURIxX2Qw6JYQ2K9W VKwCNvb8tOItpvb01FuG1+dFKZa1Uegec3aHE53/4hl14PSxwLW9D1kcqmlLVntoE8od p5tA== X-Received: by 10.194.76.137 with SMTP id k9mr36387847wjw.29.1356364285615; Mon, 24 Dec 2012 07:51:25 -0800 (PST) Received: from dragon.dg (41-132-132-229.dsl.mweb.co.za. [41.132.132.229]) by mx.google.com with ESMTPS id s16sm39056243wii.0.2012.12.24.07.51.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Dec 2012 07:51:24 -0800 (PST) From: David Naylor To: freebsd-questions@freebsd.org Subject: Re: Wine-fbsd64 updated to 1.5.18 (32bit Wine for 64bit FreeBSD) Date: Mon, 24 Dec 2012 17:51:14 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.9.1; amd64; ; ) References: <201212011521.21180.naylor.b.david@gmail.com> In-Reply-To: <201212011521.21180.naylor.b.david@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1425665.JJyC8MQ2m6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201212241751.17040.naylor.b.david@gmail.com> Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 15:51:27 -0000 --nextPart1425665.JJyC8MQ2m6 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Apologies, the incorrect package was uploaded for wine-1.5.x-freebsd9 for=20 wine-fbsd64-1.5.18. The correct file is: MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) =3D f256fb13adaf5c8bf313c5973ac8159c Regards, David On Saturday, 1 December 2012 15:21:14 David Naylor wrote: > Hi, >=20 > Packages [1] for wine-fbsd64-1.5.18 have been uploaded to mediafire [2].= =20 > The packages for FreeBSD 10 use the pkgng [3] format. >=20 > Please read the installation messages, if you use the nVidia graphics > driver, for further information. >=20 > FAQ > --- > Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: > Undefined symbol "_ThreadRuneLocale" > A: This problem is specific to FreeBSD-9.0, please either stick with > wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). > Apologies for the inconvenience. >=20 > Q: Creating pkgng packages for FreeBSD-9 > A: When there is no demand for FreeBSD-8 packages I'll create additional > pkgng packages for FreeBSD-9. Since it is possible to install the > existing pkg packages in a pkgng environment (which I do) this is not a > high priority. >=20 > Q: Wine doesn't run (properly) with a clang built world > A: Clang was compiling i386 on a 16-byte boundary while gcc was using a > 4-byte boundary. To fix, recompile world after ensuring your sources > include http://beta.freshbsd.org/commit/freebsd/r242835 or the relevant > MFC. >=20 > Regards, >=20 > David >=20 > [1] > MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.18,1.tbz) =3D > 7335bcf8fd3a3bcb98a74e2b9d797963 > MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.18.1.txz) =3D > 6fb7d760ffe9ef19457982e861e84f83 > MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.18,1.txz) =3D > 13c54f14d4f51e46f1b22320b41308ca > [2] http://www.mediafire.com/wine_fbsd64 > [3] http://wiki.freebsd.org/pkgng --nextPart1425665.JJyC8MQ2m6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlDYefUACgkQUaaFgP9pFrLTVACfX2nFWglpANORYO4m8vzZUiWH v9QAn1rG2iBT2zvgzQJSnNUhdLzYVoUO =Xooc -----END PGP SIGNATURE----- --nextPart1425665.JJyC8MQ2m6-- From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 25 08:33:49 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72A1491D; Tue, 25 Dec 2012 08:33:49 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id BC8B18FC15; Tue, 25 Dec 2012 08:33:48 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id o1so6638999wic.5 for ; Tue, 25 Dec 2012 00:33:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=gft0Bz/qL7FwPmiHPVi9PMyxLkGKngDpXem0+ZyDGm8=; b=Nj++vxplGx+PfjK/Nm6jS3jx0+KExLUk2zw19wgmxaZW0Spv4Y4YZsMZ/20QZwMj3x Qn5ol10ZUdHIat4a9iasFY5urBz1vhoa/bqeUNSWWjyo7gs4ssU101404nsMb0PHFezi XrEq3noY1sW6tDVqccN2EMtssDR43UbeKWA1Odryn7NLZgw/p7Eq3Eevpg8CoAmVMBB5 Ztljk/4zGpIpq8nIyrxyWuM/nJ1vBPpKnfaRHwHaYohznUAHrSyM9MPrz2A4lJp3e+/h pnsevYjv9wPnXR6KXlq/xSJfiW/ctmrBeqFA4+vWCdKOdGcpZmjlRbufKI2BX9QY4WSP dkxw== X-Received: by 10.194.236.166 with SMTP id uv6mr38873806wjc.34.1356424421786; Tue, 25 Dec 2012 00:33:41 -0800 (PST) Received: from dragon.dg (41-132-132-229.dsl.mweb.co.za. [41.132.132.229]) by mx.google.com with ESMTPS id s16sm42255305wii.0.2012.12.25.00.33.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Dec 2012 00:33:40 -0800 (PST) From: David Naylor To: Ross Subject: Re: Sound lag in Wine Date: Tue, 25 Dec 2012 10:33:32 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.9.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1768253.drIfEMAh01"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201212251033.35617.naylor.b.david@gmail.com> Cc: freebsd-emulation@freebsd.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 08:33:49 -0000 --nextPart1768253.drIfEMAh01 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi On Thursday, 20 December 2012 15:08:31 Ross wrote: > Hello. >=20 > I installed David Naylor's wine-fbsd64-1.5.18. > Installed Steam, bought Counter-Strike 1.6 and CS: CZ. >=20 > However, when I run these games I experience a sound lag (maybe a > half-second =E2=80=94 second). I remember having a similar problem, although my issue was an echo. After = a=20 few updates the issue disappeared. =20 > I googled the topic, the soultion is to switch to Alsa, which is not > supported in wine-fbsd64-1.5.18=E2=80=A6 >=20 > Is there anything I can do to get rid of the lag? I can suggest three things to try: 1) Update software 1.1) Upgrade (or downgrade) wine (I've release version 1.5.20) 1.2) Upgrade ports (some sound related components may cause issues, althou= gh=20 *very* unlikely) 1.3) Upgrade kernel and world (sound fixes may be available to fix your=20 issue) =20 2) Try building your own wine package with ALSA support (requires a i386=20 jail/chroot, editing the emulators/wine-devel/Makefile and manually install= ing=20 the ALSA port). See my other emails regarding the procedure to build a win= e- fbsd64 package. =20 3) File a bug report to bugs.winehq.org. I've found the sound guy very=20 responsive and willing to fix the OSS backend (patches may be provided=20 requiring parts of step 2). =20 If you do not come right please ping me in the middle of Jan and I'll try=20 assist you (I should be able to get a copy of CS 1.6). =20 Regards, David --nextPart1768253.drIfEMAh01 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlDZZN8ACgkQUaaFgP9pFrIqFQCfbDNedakx+LtIQfrmizK1p3LA 4dMAn3bwsluYqS3VOKRUKPgxnN4nkWbv =iniA -----END PGP SIGNATURE----- --nextPart1768253.drIfEMAh01-- From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 25 09:22:24 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 90AAEFCB for ; Tue, 25 Dec 2012 09:22:24 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 1EDAC8FC0C for ; Tue, 25 Dec 2012 09:22:24 +0000 (UTC) Received: from [188.174.193.9] (helo=localhost.my.domain) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TnQiL-0007W2-1k; Tue, 25 Dec 2012 10:22:21 +0100 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.my.domain (8.14.4/8.14.3) with ESMTP id qBP9MIID002856; Tue, 25 Dec 2012 10:22:19 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.14.4/8.14.3/Submit) id qBP9MIHD002855; Tue, 25 Dec 2012 10:22:18 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Tue, 25 Dec 2012 10:22:17 +0100 From: Matthias Apitz To: freebsd-emulation@freebsd.org, David Naylor Subject: Wine: Sony Reader for PC software in wine Message-ID: <20121225092217.GA2710@tinyCurrent> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 9.0-CURRENT r214444 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 188.174.193.9 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Matthias Apitz List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 09:22:24 -0000 Hello FreeBSD wine guru's, I owned an ebook reader Sony PRS-T1 which can be connected via USB to a Windows, Mac or UNIX PC to transfer files (epub, PDF, ...) or other purpose. On connect via USB it offers a FAT and a FAT32 file system, which can be mounted in Linux or FreeBSD fine. One seems to be containing firmware (it appears in Windows as K:(SETTINGS)), while the other (F:(READER)) contains the media files. The device itself runs some kind of Linux, perhaps an Android and it is possible to root it (not yet done by me). Sony delivers for free some software for Win and MAC, the so called "Sony Reader for PC", which allows: - import of DRM'ed epub files - use (i.e. human read) the files with your Adobe account ID - authorise the T1 against the Adobe servers with your ID - transfer DRM'ed files to the T1 to be read there The software installs fine with wine 1.5.4 and it starts fine with: $ wine Reader.exe One can connect fine to the Adobe ID server, import and read DRM'ed epubs. What does not work is that the T1 on the USB devices is not seen. I have mounted the two USB devices as: /dev/da2 on /settings (msdosfs, local, read-only) /dev/da0 on /reader (msdosfs, local) and configured wine (with winecfg) to see the devices as K: and F: which works fine, for example, with the Explorer.exe; but the software Reader.exe does not "see" the T1; it says on start: fixme:win:FlashWindowEx 0x33f228 fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail fixme:iphlpapi:NotifyAddrChange (Handle 0x79f6e0, overlapped 0x100cf2a0): stub fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub fixme:win:RegisterDeviceNotificationA (hwnd=0x700f8, filter=0xb6ed48,flags=0x00000000) returns a fake device notification handle! fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! fixme:win:FlashWindowEx 0x33d450 and in the GUI it says that the reader T1 is not connected. Perhaps the software is reading somehow the USB bus directly and looking for the vendorID and productID... How I could nail down, what it is missing? Thanks matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 25 14:28:27 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 95D7B79D for ; Tue, 25 Dec 2012 14:28:27 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by mx1.freebsd.org (Postfix) with ESMTP id 10C948FC13 for ; Tue, 25 Dec 2012 14:28:26 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id r6so3738057wey.10 for ; Tue, 25 Dec 2012 06:28:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; bh=IWrO56Lh5o8xyrC4d+hDwfUgr2KAt5BnQTazce/NpAk=; b=jQ6bQAuMXVBR+OtsVB6gLV0GZOnFr7PzoLtsYVV0O7ByhkHSH2xqdAL4oloY3RCxFd LQm3synzq+HlrsR7R38YlU4u+3heLbsgOl1MO31uCIcFwwiSgZc2acZB40IeT3XH2qOE 8zLLHXSDVaWR/jCQ8ZmVp+QNNkVv6TAmIrL7mRG2k/JURe6+MTIZg8PcC6bZrG4QKz9A HCQdY/JMkXCEyC5qkqiUvM8muxKKmIhC41roNR2DRs9IiUP1c6gzDS7KmM5LWy+e070E Y3KCidzUdKL5q0TDOkmo4NtBI/VXyxbNNqsWihMYt0349M8f5VjMASLBfMpO62UjxHwH ROVQ== X-Received: by 10.194.88.98 with SMTP id bf2mr40033632wjb.49.1356445699786; Tue, 25 Dec 2012 06:28:19 -0800 (PST) Received: from dragon.dg (41-132-132-229.dsl.mweb.co.za. [41.132.132.229]) by mx.google.com with ESMTPS id df2sm38862921wib.0.2012.12.25.06.28.17 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Dec 2012 06:28:18 -0800 (PST) From: David Naylor To: Matthias Apitz Subject: Re: Wine: Sony Reader for PC software in wine Date: Tue, 25 Dec 2012 16:28:10 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.9.1; amd64; ; ) References: <20121225092217.GA2710@tinyCurrent> In-Reply-To: <20121225092217.GA2710@tinyCurrent> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2041843.MYLOz5uuqI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201212251628.13844.naylor.b.david@gmail.com> Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 14:28:27 -0000 --nextPart2041843.MYLOz5uuqI Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, On Tuesday, 25 December 2012 11:22:17 Matthias Apitz wrote: > Hello FreeBSD wine guru's, >=20 > The software installs fine with wine 1.5.4 and it starts fine with: Could you try with a newer version of wine, wine up to 1.5.20 has been=20 released. =20 > $ wine Reader.exe >=20 > One can connect fine to the Adobe ID server, import and read DRM'ed > epubs. What does not work is that the T1 on the USB devices is not seen. >=20 > I have mounted the two USB devices as: >=20 > /dev/da2 on /settings (msdosfs, local, read-only) > /dev/da0 on /reader (msdosfs, local) >=20 > and configured wine (with winecfg) to see the devices as K: and F: which > works fine, for example, with the Explorer.exe; but the software > Reader.exe does not "see" the T1; it says on start: >=20 > fixme:win:FlashWindowEx 0x33f228 > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections > will fail fixme:iphlpapi:NotifyAddrChange (Handle 0x79f6e0, overlapped > 0x100cf2a0): stub fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: > heap list snapshot fixme:toolhelp:Heap32ListFirst : stub > fixme:win:RegisterDeviceNotificationA (hwnd=3D0x700f8, > filter=3D0xb6ed48,flags=3D0x00000000) returns a fake device notification > handle! fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:win:FlashWindowEx 0x33d450 The line fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 suggests to me that wine does not implement some functionality that Reader.= exe=20 requires... > and in the GUI it says that the reader T1 is not connected. Perhaps > the software is reading somehow the USB bus directly and looking for the > vendorID and productID... >=20 > How I could nail down, what it is missing? Thanks You could try appdb.winehq.org and see if the software is supported. The=20 website may also suggest fixes for various issues. If there is no page for= =20 the software try filing a bug report, if there is a page then look through = the=20 bug reports to see if focus is given to fix it. =20 It is possible that this is a FreeBSD specific problem, in which case=20 submitting a bug report may be required. =20 Lastly, look at documentation for the WINEDEBUG environment variable as tha= t=20 could provide more information as to the source of the error. =20 Good luck.=20 Regards, --nextPart2041843.MYLOz5uuqI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlDZt/0ACgkQUaaFgP9pFrJ0RgCghBJ7LM/fGYysbapi7oQ8FzIt eqEAn3ufrTBDRVgzjsve02x0caV3nFJv =3Pqb -----END PGP SIGNATURE----- --nextPart2041843.MYLOz5uuqI-- From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 25 21:52:41 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 364A2735 for ; Tue, 25 Dec 2012 21:52:41 +0000 (UTC) (envelope-from pz-freebsd-emulation@ziemba.us) Received: from ziemba.us (osmtp.ziemba.us [208.106.105.149]) by mx1.freebsd.org (Postfix) with ESMTP id EDA718FC0C for ; Tue, 25 Dec 2012 21:52:40 +0000 (UTC) Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1]) by hairball.ziemba.us (8.14.5/8.14.5) with ESMTP id qBPLMbEi053683 for ; Tue, 25 Dec 2012 13:22:37 -0800 (PST) (envelope-from pz-freebsd-emulation@ziemba.us) Received: (from mailnull@localhost) by hairball.ziemba.us (8.14.5/8.14.5/Submit) id qBPLMbrR053682 for freebsd-emulation@freebsd.org; Tue, 25 Dec 2012 13:22:37 -0800 (PST) (envelope-from pz-freebsd-emulation@ziemba.us) X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to pz-freebsd-emulation@ziemba.us using -f Received: (from news@localhost) by usenet.ziemba.us (8.14.5/8.14.5/Submit) id qBPLMX8Z058135 for treehouse-mail-freebsd-emulation@hairball.ziemba.us; Tue, 25 Dec 2012 13:22:33 -0800 (PST) (envelope-from news) From: "G. Paul Ziemba" To: freebsd-emulation@freebsd.org Subject: How do I prevent host usb wifi driver from attaching? Date: Tue, 25 Dec 2012 21:22:33 +0000 (UTC) Message-id: Errors-to: "G. Paul Ziemba" X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: paul+usenet@w6yx.stanford.edu List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 21:52:41 -0000 I'm running FreeBSD 8.2-STABLE (host) and VirtualBox 4.2.0. I have followed the steps in http://wiki.freebsd.org/VirtualBox to make USB devices available to VirtualBox guests, and that works (e.g., a Win2K guest can use a USB scanner I have attached to the host's USB interface). I'm planning another guest running FreeBSD (probably 9.X) and I'd like to have a USB wifi dongle (probably a run(4) device) that is visible to the guest as a network interface, but that is not visible to the host. I think this can be accomplished by preventing the run(4) driver on the host from seizing the usb device, and then configuring VirtualBox to let that USB device be visible to the guest. I think I can prevent the host's usb driver from loading by editing (or overriding?) the matching entry in /etc/devd/usb.conf which would prevent the run(4) module from loading, but that's kind of a big hammer. Has anyone else solved a similar problem? Is there a finer-grained approach? thanks, ~!paul -- G. Paul Ziemba FreeBSD unix: 1:21PM up 22 days, 18:59, 19 users, load averages: 0.41, 0.37, 0.30 From owner-freebsd-emulation@FreeBSD.ORG Tue Dec 25 22:23:04 2012 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE2AD876 for ; Tue, 25 Dec 2012 22:23:04 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id A2FF08FC13 for ; Tue, 25 Dec 2012 22:23:04 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 8A1FB1E007A3; Tue, 25 Dec 2012 23:22:57 +0100 (CET) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.5/8.14.4) with ESMTP id qBPMLB11066874; Tue, 25 Dec 2012 23:21:11 +0100 (CET) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.5/8.14.3/Submit) id qBPMLApo066873; Tue, 25 Dec 2012 23:21:10 +0100 (CET) (envelope-from nox) Date: Tue, 25 Dec 2012 23:21:10 +0100 (CET) From: Juergen Lock Message-Id: <201212252221.qBPMLApo066873@triton8.kn-bremen.de> To: feld@feld.me Subject: Re: [linux-f10-flashplugin11] Flash colors messed up, red shown as blue, probably due to the hardware acceleration X-Newsgroups: local.list.freebsd.emulation In-Reply-To: <6478adcb-f45c-433c-ab5a-aa737e0cb450@email.android.com> References: <50CC174A.7040506@rawbw.com> <20121217081716.4353e598@tech304> <20121218062223.55f8179b@tech304> Organization: Cc: freebsd-emulation@FreeBSD.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 22:23:05 -0000 In article <6478adcb-f45c-433c-ab5a-aa737e0cb450@email.android.com> you write: >I'll compare to mine when I get home. Perhaps this is a new bug? The bug is old, just the fix hasn't reached ports yet. (Yes the bug is in flash and there's a workaround in libvdpau now, but since flash is Linux code it's the _Linux_ libvdpau that needs the workaround, i.e. /compat/linux/usr/lib/libvdpau.so.* not /usr/local/lib/libvdpau.so.* and the former is installed by the nvidia-driver port which currently is at a version that doesn't have the fix yet.) So you need to either disable vdpau for flash in flash's context menu _or_ grab the latest Linux(!) libvdpau out of (for example) Nvidia's latest driver tarball. [1] Well, or wait until the nvidia-driver port gets updated... HTH, Juergen [1] I tested the one in NVIDIA-FreeBSD-x86_64-310.19.tar.gz and also found the workaround needs linprocfs(5) mounted for the running-in-flash detection to work. From owner-freebsd-emulation@FreeBSD.ORG Wed Dec 26 07:28:19 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4177227F for ; Wed, 26 Dec 2012 07:28:19 +0000 (UTC) (envelope-from jan0sch@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id BCAF78FC0A for ; Wed, 26 Dec 2012 07:28:18 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.27]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MCeui-1Tvycd2SaA-009QhT for ; Wed, 26 Dec 2012 08:28:17 +0100 Received: (qmail invoked by alias); 26 Dec 2012 07:28:17 -0000 Received: from dslb-088-072-242-114.pools.arcor-ip.net (EHLO magni.rostock.home) [88.72.242.114] by mail.gmx.net (mp027) with SMTP; 26 Dec 2012 08:28:17 +0100 X-Authenticated: #1545395 X-Provags-ID: V01U2FsdGVkX1+ZM2NC5MKZd4ORZk8ZSY4/wmN83z4iIvL7wJ2yys 6h4HxMGZr3qkx/ Date: Wed, 26 Dec 2012 08:27:55 +0100 From: Jens Jahnke To: David Naylor Subject: Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD) Message-Id: <20121226082755.ee1d4a3077742aa0ff1638e2@gmx.net> In-Reply-To: <201212241227.15165.naylor.b.david@gmail.com> References: <201212241227.15165.naylor.b.david@gmail.com> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.3) X-Face: &?!P`87-36gaG)/K:yi&ixw=uy]y'?$vrc Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA512"; boundary="Signature=_Wed__26_Dec_2012_08_27_55_+0100_eS0ICN0K1Kc.OU9e" X-Y-GMX-Trusted: 0 Cc: freebsd-emulation@freebsd.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Dec 2012 07:28:19 -0000 --Signature=_Wed__26_Dec_2012_08_27_55_+0100_eS0ICN0K1Kc.OU9e Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, 24 Dec 2012 12:27:11 +0200 David Naylor wrote: DN> Since it is possible to install the existing pkg=20 DN> packages in a pkgng environment (which I do) this is not a high DN> priority. is there a documentation for that? I searched the pkgng docs but found nothing regarding installation of "old" packages or converting them to a newer version. Regards, Jens --=20 26. Julmond 2012, 08:27 Homepage : http://www.jan0sch.de What the world *really* needs is a good Automatic Bicycle Sharpener. --Signature=_Wed__26_Dec_2012_08_27_55_+0100_eS0ICN0K1Kc.OU9e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQG8BAEBCgAGBQJQ2qcPAAoJED2+SXzzbciG9dkM/A4WM+QGiq6P4+gVLPBf45Xn d0W95tdUfaCKPk4TvpTtN+y//JZAZ+R2LFApBpN64jxTzXHd+tIG2E6iJRGaYT6V WacbUOtjnURwzzfA2NSfOtSpvE1CeZbW5S/f+zCcrpawzGVeXyJD+ufBuplea1Ri 97iB6PYaHM7QCk3WsS+z/yGrtQoGvZ0n4xrDCn4xwp2mWvtB58vuhPNUFApaaEPY Xs0hCeFoNGP8PtX4NDuuE8KAjwY4uEQp8FFTQ1/G6vn53XeJ6beB4Mw3IayTkkDQ 5XriveIDx8jE84akDkbVP0DyVbjMx9elyxRrPoN8bKAp5BGoCLYY4NRtu6QSK5C+ j18cczJDMGHZ5dpJCdTiaZYpQVdFEJIfwJNWII8dHKTXK2Rkp/TJ440OaDcPiobf gT/H9u+oXMDvo+kpsDg/tA9NeD05uUORIsJiCh2B3vtpPy+5mXU4kf7/gYpCF6lo niY4bfxQ+IHPyznotFA2QH4IOOUCtESekNOBD0TR1gDiycbSWgKKkvSD8HapuJtl 4Wvh+d43jfsVwalhkBEH =l0Lq -----END PGP SIGNATURE----- --Signature=_Wed__26_Dec_2012_08_27_55_+0100_eS0ICN0K1Kc.OU9e-- From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 27 00:30:28 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD59ECB5 for ; Thu, 27 Dec 2012 00:30:28 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [99.69.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id 407F78FC08 for ; Thu, 27 Dec 2012 00:30:27 +0000 (UTC) Received: from vixen42.vulpes.vvelox.net (vixen42.vulpes.vvelox.net [192.168.15.2]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id 22ED33F71A; Wed, 26 Dec 2012 18:19:19 -0600 (CST) Date: Wed, 26 Dec 2012 18:21:03 -0600 From: "Zane C. B-H." To: Ross Subject: Re: Sound lag in Wine Message-ID: <20121226182103.698bfe55@vixen42.vulpes.vvelox.net> In-Reply-To: References: X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2012 00:30:28 -0000 T24gVGh1LCAyMCBEZWMgMjAxMiAxNTowODozMSArMDIwMA0KUm9zcyA8YmFzYXJldnljaEBnbWFp bC5jb20+IHdyb3RlOg0KDQo+IEhlbGxvLg0KPiANCj4gSSBpbnN0YWxsZWQgRGF2aWQgTmF5bG9y J3Mgd2luZS1mYnNkNjQtMS41LjE4Lg0KPiBJbnN0YWxsZWQgU3RlYW0sIGJvdWdodCBDb3VudGVy LVN0cmlrZSAxLjYgYW5kIENTOiBDWi4NCj4gDQo+IEhvd2V2ZXIsIHdoZW4gSSBydW4gdGhlc2Ug Z2FtZXMgSSBleHBlcmllbmNlIGEgc291bmQgbGFnIChtYXliZSBhDQo+IGhhbGYtc2Vjb25kIOKA lCBzZWNvbmQpLg0KPiANCj4gSSBnb29nbGVkIHRoZSB0b3BpYywgdGhlIHNvdWx0aW9uIGlzIHRv IHN3aXRjaCB0byBBbHNhLCB3aGljaCBpcyBub3QNCj4gc3VwcG9ydGVkIGluIHdpbmUtZmJzZDY0 LTEuNS4xOOKApg0KPiANCj4gSXMgdGhlcmUgYW55dGhpbmcgSSBjYW4gZG8gdG8gZ2V0IHJpZCBv ZiB0aGUgbGFnPw0KDQpObyBjbHVlIGlmIHRoaXMgaXMgaXQsIGJ1dCBJIHdvdWxkIHN0cm9uZ2x5 IHN1Z2dlc3QgdHVybmluZyBvZmYNCmhhcmR3YXJlIGFjY2VsZXJhdGlvbiBmb3IgYXVkaW8gaWYg dGhlcmUgaXMgYW4gb3B0aW9uIGZvciBpdCBwcmVzZW50DQppbiB0aGUgb3B0aW9ucyBmb3IgdGhh dCBnYW1lLg0KDQpUaGF0IGlzIHNvbWV0aGluZyBJJ3ZlIHNlZW4gY2F1c2UgYWxsIHNvcnRzIG9m IHdlaXJkIGlzc3VlcyBiZWZvcmUgaW4NCnRoZSBwYXN0Lg0K From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 27 09:48:03 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7D81DA; Thu, 27 Dec 2012 09:48:03 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2AE8FC08; Thu, 27 Dec 2012 09:48:02 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 322D07300B; Thu, 27 Dec 2012 10:46:49 +0100 (CET) Date: Thu, 27 Dec 2012 10:46:49 +0100 From: Luigi Rizzo To: current@freebsd.org, jfvogel@gmail.com Subject: [RFC] proposed 'lem' patch to improve behaviour under emulation Message-ID: <20121227094649.GA48891@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2012 09:48:03 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline This patch implements two features for the 'lem' driver that greatly improve the throughput under proper hypervisor. This is joint work with Vincenzo Maffione and Giuseppe Lettieri, I am posting it here for review, will then commit it if there are no objections. The first change is to implement a sysctl to access the 'itr' interrupt moderation register for the devices supported by this driver. It is little more than adding a struct into the device descriptor, and one line to create the dynamic sysctl entry, same as it is done for the other mitigation registers. The second change is more interesting and has huge benefits on througput. Under virtualization, "VM exits" (which happen every time there is an access to a register of the emulated peripheral) are extremely expensive. In the tx path of the 'lem' driver, there is a write to the TDT register on every packet sent. The patch we propose, if enabled through a sysctl (defaults off, so no change from current behaviour) defers writes to the TDT register when there is a pending transmit interrupt. This means that, together with proper emulation of interrupt mitigation on the hypervisor side, the number of VM exits is dramatically reduced. To give you an idea, on a modern system with qemu-kvm and companion patches, UDP throughput is KVM QEMU standard KVM, standard driver 20 Kpps 6.3 Kpps modified KVM, standard driver 37 Kpps 28 Kpps modified KVM, modified driver 200 Kpps 34 Kpps As you can see, on kvm this change gives a 5x speedup to the tx path, which combines nicely with the 2x speedup that comes from supporting interrupt mitigation alone in the hypervisor. Without kvm (or kqemu ?) the benefits are much lower, as the guest becomes too slow. Patch follows. It would be good if people with real hardware using the 'lem' driver could test it to make sure it does no harm on their devices (in any case the sysctl variable dev.em.0.mit_enable must be set to explicitly enable it at runtime). (for those curious to test it under kvm, i am also attaching a patch that you need to apply to qemu in order to exploit the effect of interrupt mitigation; it is a followup of a similar patch i posted in july to the qemu mailing list, and i will post it the update there as well, shortly. Unfortunately we do not have kvm on freebsd..) cheers luigi --wRRV7LY7NUeQGEoC Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="patch-e1000-emulation-20121227.diff" Index: if_lem.c =================================================================== --- if_lem.c (revision 244673) +++ if_lem.c (working copy) @@ -32,6 +32,8 @@ ******************************************************************************/ /*$FreeBSD$*/ +#define MITIGATION + #ifdef HAVE_KERNEL_OPTION_HEADERS #include "opt_device_polling.h" #include "opt_inet.h" @@ -281,6 +283,9 @@ #define EM_TICKS_TO_USECS(ticks) ((1024 * (ticks) + 500) / 1000) #define EM_USECS_TO_TICKS(usecs) ((1000 * (usecs) + 512) / 1024) +#define MAX_INTS_PER_SEC 8000 +#define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) + static int lem_tx_int_delay_dflt = EM_TICKS_TO_USECS(EM_TIDV); static int lem_rx_int_delay_dflt = EM_TICKS_TO_USECS(EM_RDTR); static int lem_tx_abs_int_delay_dflt = EM_TICKS_TO_USECS(EM_TADV); @@ -442,6 +447,11 @@ &adapter->tx_abs_int_delay, E1000_REGISTER(&adapter->hw, E1000_TADV), lem_tx_abs_int_delay_dflt); + lem_add_int_delay_sysctl(adapter, "itr", + "interrupt delay limit in usecs/4", + &adapter->tx_itr, + E1000_REGISTER(&adapter->hw, E1000_ITR), + DEFAULT_ITR); } /* Sysctls for limiting the amount of work done in the taskqueue */ @@ -449,6 +459,12 @@ "max number of rx packets to process", &adapter->rx_process_limit, lem_rx_process_limit); +#ifdef MITIGATION + /* Sysctls to control mitigation */ + lem_add_rx_process_limit(adapter, "mit_enable", + "driver TDT mitigation", &adapter->mit_enable, 0); +#endif /* MITIGATION */ + /* Sysctl for setting the interface flow control */ lem_set_flow_cntrl(adapter, "flow_control", "flow control setting", @@ -1702,6 +1718,17 @@ */ bus_dmamap_sync(adapter->txdma.dma_tag, adapter->txdma.dma_map, BUS_DMASYNC_PREREAD | BUS_DMASYNC_PREWRITE); +#ifdef MITIGATION + if (adapter->mit_enable) { + if (adapter->shadow_tdt & MIT_PENDING_INT) { + /* signal intr and data pending */ + adapter->shadow_tdt = MIT_PENDING_TDT | (i & 0xffff); + return (0); + } else { + adapter->shadow_tdt = MIT_PENDING_INT; + } + } +#endif /* MITIGATION */ if (adapter->hw.mac.type == e1000_82547 && adapter->link_duplex == HALF_DUPLEX) lem_82547_move_tail(adapter); @@ -3027,6 +3054,16 @@ adapter->next_tx_to_clean = first; adapter->num_tx_desc_avail = num_avail; +#ifdef MITIGATION + if ((adapter->shadow_tdt & MIT_PENDING_TDT) == MIT_PENDING_TDT) { + /* a tdt write is pending, do it */ + E1000_WRITE_REG(&adapter->hw, E1000_TDT(0), + 0xffff & adapter->shadow_tdt); + adapter->shadow_tdt = MIT_PENDING_INT; + } else { + adapter->shadow_tdt = 0; // disable + } +#endif /* MITIGATION */ /* * If we have enough room, clear IFF_DRV_OACTIVE to * tell the stack that it is OK to send packets. @@ -3246,8 +3283,6 @@ * Enable receive unit. * **********************************************************************/ -#define MAX_INTS_PER_SEC 8000 -#define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) static void lem_initialize_receive_unit(struct adapter *adapter) @@ -4588,6 +4623,8 @@ return (EINVAL); info->value = usecs; ticks = EM_USECS_TO_TICKS(usecs); + if (info->offset == E1000_ITR) /* units are 256ns here */ + ticks *= 4; adapter = info->adapter; Index: if_lem.h =================================================================== --- if_lem.h (revision 244673) +++ if_lem.h (working copy) @@ -363,6 +363,7 @@ struct em_int_delay_info tx_abs_int_delay; struct em_int_delay_info rx_int_delay; struct em_int_delay_info rx_abs_int_delay; + struct em_int_delay_info tx_itr; /* * Transmit definitions @@ -436,6 +437,13 @@ boolean_t pcix_82544; boolean_t in_detach; +#ifdef MITIGATION + /* values for shadow_tdt: 0 = idle, 16-low bits: tdt) */ +#define MIT_PENDING_INT 0x10000 /* pending interrupt */ +#define MIT_PENDING_TDT 0x30000 /* both intr and tdt write are pending */ + uint32_t shadow_tdt; + uint32_t mit_enable; /* control driver tx mitigation */ +#endif /* MITIGATION */ struct e1000_hw_stats stats; }; --wRRV7LY7NUeQGEoC Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="patch-qemu-mitigation-20121227.diff" diff -urp qemu-1.3.0-orig/hw/e1000.c qemu-1.3.0/hw/e1000.c --- qemu-1.3.0-orig/hw/e1000.c 2012-12-03 20:37:05.000000000 +0100 +++ qemu-1.3.0/hw/e1000.c 2012-12-27 09:47:16.000000000 +0100 @@ -35,6 +35,8 @@ #include "e1000_hw.h" +static int mit_on = 1; /* interrupt mitigation enable */ + #define E1000_DEBUG #ifdef E1000_DEBUG @@ -129,6 +131,9 @@ typedef struct E1000State_st { } eecd_state; QEMUTimer *autoneg_timer; + QEMUTimer *mit_timer; // handle for the timer + uint32_t mit_timer_on; // mitigation timer active + uint32_t mit_cause; // pending interrupt cause } E1000State; #define defreg(x) x = (E1000_##x>>2) @@ -144,6 +149,7 @@ enum { defreg(TPR), defreg(TPT), defreg(TXDCTL), defreg(WUFC), defreg(RA), defreg(MTA), defreg(CRCERRS),defreg(VFTA), defreg(VET), + defreg(RDTR), defreg(RADV), defreg(TADV), defreg(ITR), }; static void @@ -639,6 +645,68 @@ static uint64_t tx_desc_base(E1000State return (bah << 32) + bal; } +/* helper function, 0 means the value is not set */ +static inline void +mit_update_delay(uint32_t *curr, uint32_t value) +{ + if (value && (*curr == 0 || value < *curr)) + *curr = value; +} + +/* + * If necessary, rearm the timer and post an interrupt. + * Called at the end of tx/rx routines (mit_timer_on == 0), + * and when the timer fires (mit_timer_on == 1). + * We provide a partial implementation of interrupt mitigation, + * emulating only RADV, TADV and ITR (lower 16 bits, 1024ns units for + * RADV and TADV, 256ns units for ITR). RDTR is only used to enable RADV; + * relative timers based on TIDV and RDTR are not implemented. + */ +static void +mit_rearm_and_int(void *opaque) +{ + E1000State *s = opaque; + uint32_t mit_delay = 0; + + /* + * Clear the flag. It is only set when the callback fires, + * and we need to clear it anyways. + */ + s->mit_timer_on = 0; + if (s->mit_cause == 0) /* no events pending, we are done */ + return; + /* + * Compute the next mitigation delay according to pending interrupts + * and the current values of RADV (provided RDTR!=0), TADV and ITR. + * Then rearm the timer. + */ + if (s->mit_cause & (E1000_ICR_TXQE | E1000_ICR_TXDW)) + mit_update_delay(&mit_delay, s->mac_reg[TADV] * 4); + if (s->mac_reg[RDTR] && (s->mit_cause & E1000_ICS_RXT0)) + mit_update_delay(&mit_delay, s->mac_reg[RADV] * 4); + mit_update_delay(&mit_delay, s->mac_reg[ITR]); + + if (mit_delay) { + s->mit_timer_on = 1; + qemu_mod_timer(s->mit_timer, + qemu_get_clock_ns(vm_clock) + mit_delay * 256); + } + set_ics(s, 0, s->mit_cause); + s->mit_cause = 0; +} + +static void +mit_set_ics(E1000State *s, uint32_t cause) +{ + if (mit_on == 0) { + set_ics(s, 0, cause); + return; + } + s->mit_cause |= cause; + if (!s->mit_timer_on) + mit_rearm_and_int(s); +} + static void start_xmit(E1000State *s) { @@ -676,7 +744,7 @@ start_xmit(E1000State *s) break; } } - set_ics(s, 0, cause); + mit_set_ics(s, cause); } static int @@ -894,7 +962,7 @@ e1000_receive(NetClientState *nc, const s->rxbuf_min_shift) n |= E1000_ICS_RXDMT0; - set_ics(s, 0, n); + mit_set_ics(s, n); return size; } @@ -999,6 +1067,7 @@ static uint32_t (*macreg_readops[])(E100 getreg(RDH), getreg(RDT), getreg(VET), getreg(ICS), getreg(TDBAL), getreg(TDBAH), getreg(RDBAH), getreg(RDBAL), getreg(TDLEN), getreg(RDLEN), + getreg(RDTR), getreg(RADV), getreg(TADV), getreg(ITR), [TOTH] = mac_read_clr8, [TORH] = mac_read_clr8, [GPRC] = mac_read_clr4, [GPTC] = mac_read_clr4, [TPR] = mac_read_clr4, [TPT] = mac_read_clr4, @@ -1015,6 +1084,8 @@ static void (*macreg_writeops[])(E1000St putreg(PBA), putreg(EERD), putreg(SWSM), putreg(WUFC), putreg(TDBAL), putreg(TDBAH), putreg(TXDCTL), putreg(RDBAH), putreg(RDBAL), putreg(LEDCTL), putreg(VET), + [RDTR] = set_16bit, [RADV] = set_16bit, [TADV] = set_16bit, + [ITR] = set_16bit, [TDLEN] = set_dlen, [RDLEN] = set_dlen, [TCTL] = set_tctl, [TDT] = set_tctl, [MDIC] = set_mdic, [ICS] = set_ics, [TDH] = set_16bit, [RDH] = set_16bit, [RDT] = set_rdt, @@ -1286,6 +1357,9 @@ static int pci_e1000_init(PCIDevice *pci add_boot_device_path(d->conf.bootindex, &pci_dev->qdev, "/ethernet-phy@0"); d->autoneg_timer = qemu_new_timer_ms(vm_clock, e1000_autoneg_timer, d); + d->mit_cause = 0; + d->mit_timer_on = 0; + d->mit_timer = qemu_new_timer_ns(vm_clock, mit_rearm_and_int, d); return 0; } --wRRV7LY7NUeQGEoC-- From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 27 10:26:46 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0215099F; Thu, 27 Dec 2012 10:26:46 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by mx1.freebsd.org (Postfix) with ESMTP id A57F28FC13; Thu, 27 Dec 2012 10:26:45 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id x4so8597351obh.38 for ; Thu, 27 Dec 2012 02:26:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LX/kYef3j8qMNQQ7r8FmHnV2+R35YoW3YPMJ7HkM6IA=; b=n/+oHrO13zKKMxIR+AUrkPoA8oUJMTIY3bRiQ9GjZ5q01+dcl89c0Hei0yidqvrUhR 4h53/ql86VBedlzTJgoKqPl+IS+brf0s7UTOOe6+B8ljCB6oiWB0X3XHsk5pgPxW3tZM l5ek5DEnoXvfEbZfh/veXw52MUxiNj4WNO6fCcXARHeIhb7DHMgkORxIhRS3yayvBxMs 2lc9miQJMeNcqZTxxV4pTE3sU5Obcr5VjtOnCWLX604Qf1CYU45nP2vUqABm1NKUqWqN GnCi1ujt58z5Jv+VcmPO1mYbj5Qog9yM0C9FXKGgklTFtDN4eGPQ11nRKcPaQhGJh+NX lDLw== MIME-Version: 1.0 Received: by 10.60.6.226 with SMTP id e2mr13287361oea.56.1356604004810; Thu, 27 Dec 2012 02:26:44 -0800 (PST) Received: by 10.76.143.33 with HTTP; Thu, 27 Dec 2012 02:26:44 -0800 (PST) In-Reply-To: <20121227094649.GA48891@onelab2.iet.unipi.it> References: <20121227094649.GA48891@onelab2.iet.unipi.it> Date: Thu, 27 Dec 2012 02:26:44 -0800 Message-ID: Subject: Re: [RFC] proposed 'lem' patch to improve behaviour under emulation From: Garrett Cooper To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Cc: emulation@freebsd.org, current@freebsd.org, jfvogel@gmail.com X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2012 10:26:46 -0000 On Thu, Dec 27, 2012 at 1:46 AM, Luigi Rizzo wrote: > This patch implements two features for the 'lem' driver that > greatly improve the throughput under proper hypervisor. > This is joint work with Vincenzo Maffione and Giuseppe Lettieri, > I am posting it here for review, will then commit it > if there are no objections. > > The first change is to implement a sysctl to access the 'itr' > interrupt moderation register for the devices supported by this > driver. It is little more than adding a struct into the device > descriptor, and one line to create the dynamic sysctl entry, same > as it is done for the other mitigation registers. > > The second change is more interesting and has huge benefits on througput. > > Under virtualization, "VM exits" (which happen every time there is > an access to a register of the emulated peripheral) are extremely > expensive. In the tx path of the 'lem' driver, there is a write > to the TDT register on every packet sent. > > The patch we propose, if enabled through a sysctl (defaults off, > so no change from current behaviour) defers writes to the TDT > register when there is a pending transmit interrupt. > This means that, together with proper emulation of interrupt > mitigation on the hypervisor side, the number of VM exits > is dramatically reduced. To give you an idea, on a modern > system with qemu-kvm and companion patches, UDP throughput is > > KVM QEMU > standard KVM, standard driver 20 Kpps 6.3 Kpps > modified KVM, standard driver 37 Kpps 28 Kpps > modified KVM, modified driver 200 Kpps 34 Kpps > > As you can see, on kvm this change gives a 5x speedup to the tx path, > which combines nicely with the 2x speedup that comes from supporting > interrupt mitigation alone in the hypervisor. Without kvm (or kqemu ?) > the benefits are much lower, as the guest becomes too slow. > > Patch follows. It would be good if people with real hardware > using the 'lem' driver could test it to make sure it does no > harm on their devices (in any case the sysctl variable > dev.em.0.mit_enable must be set to explicitly enable it > at runtime). > > (for those curious to test it under kvm, i am also attaching a > patch that you need to apply to qemu in order to exploit the > effect of interrupt mitigation; it is a followup of a similar > patch i posted in july to the qemu mailing list, and i will > post it the update there as well, shortly. Unfortunately > we do not have kvm on freebsd..) A few comments. Thanks! -Garrett Index: if_lem.c =================================================================== --- if_lem.c (revision 244673) +++ if_lem.c (working copy) @@ -32,6 +32,8 @@ ******************************************************************************/ /*$FreeBSD$*/ +#define MITIGATION + gcooper> Could you please make MITIGATION into a proper compile time flag via sys/conf/options with a more descript name? #ifdef HAVE_KERNEL_OPTION_HEADERS #include "opt_device_polling.h" #include "opt_inet.h" @@ -281,6 +283,9 @@ #define EM_TICKS_TO_USECS(ticks) ((1024 * (ticks) + 500) / 1000) #define EM_USECS_TO_TICKS(usecs) ((1000 * (usecs) + 512) / 1024) +#define MAX_INTS_PER_SEC 8000 +#define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) + gcooper> Add parentheses around DEFAULT_ITR (I know the code was just shuffled around, but thought I could ask :)..)? From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 27 14:00:03 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FF37B0B; Thu, 27 Dec 2012 14:00:03 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 23BA48FC17; Thu, 27 Dec 2012 14:00:01 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 7B2477300A; Thu, 27 Dec 2012 14:58:56 +0100 (CET) Date: Thu, 27 Dec 2012 14:58:56 +0100 From: Luigi Rizzo To: Garrett Cooper Subject: Re: [RFC] proposed 'lem' patch to improve behaviour under emulation Message-ID: <20121227135856.GA51105@onelab2.iet.unipi.it> References: <20121227094649.GA48891@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: emulation@freebsd.org, current@freebsd.org, jfvogel@gmail.com X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2012 14:00:03 -0000 On Thu, Dec 27, 2012 at 02:26:44AM -0800, Garrett Cooper wrote: > On Thu, Dec 27, 2012 at 1:46 AM, Luigi Rizzo wrote: > > This patch implements two features for the 'lem' driver that > > greatly improve the throughput under proper hypervisor. > > This is joint work with Vincenzo Maffione and Giuseppe Lettieri, > > I am posting it here for review, will then commit it > > if there are no objections. > > > > The first change is to implement a sysctl to access the 'itr' > > interrupt moderation register for the devices supported by this > > driver. It is little more than adding a struct into the device > > descriptor, and one line to create the dynamic sysctl entry, same > > as it is done for the other mitigation registers. > > > > The second change is more interesting and has huge benefits on througput. > > > > Under virtualization, "VM exits" (which happen every time there is > > an access to a register of the emulated peripheral) are extremely > > expensive. In the tx path of the 'lem' driver, there is a write > > to the TDT register on every packet sent. > > > > The patch we propose, if enabled through a sysctl (defaults off, > > so no change from current behaviour) defers writes to the TDT > > register when there is a pending transmit interrupt. > > This means that, together with proper emulation of interrupt > > mitigation on the hypervisor side, the number of VM exits > > is dramatically reduced. To give you an idea, on a modern > > system with qemu-kvm and companion patches, UDP throughput is > > > > KVM QEMU > > standard KVM, standard driver 20 Kpps 6.3 Kpps > > modified KVM, standard driver 37 Kpps 28 Kpps > > modified KVM, modified driver 200 Kpps 34 Kpps > > > > As you can see, on kvm this change gives a 5x speedup to the tx path, > > which combines nicely with the 2x speedup that comes from supporting > > interrupt mitigation alone in the hypervisor. Without kvm (or kqemu ?) > > the benefits are much lower, as the guest becomes too slow. > > > > Patch follows. It would be good if people with real hardware > > using the 'lem' driver could test it to make sure it does no > > harm on their devices (in any case the sysctl variable > > dev.em.0.mit_enable must be set to explicitly enable it > > at runtime). > > > > (for those curious to test it under kvm, i am also attaching a > > patch that you need to apply to qemu in order to exploit the > > effect of interrupt mitigation; it is a followup of a similar > > patch i posted in july to the qemu mailing list, and i will > > post it the update there as well, shortly. Unfortunately > > we do not have kvm on freebsd..) > > A few comments. > Thanks! > -Garrett > > Index: if_lem.c > =================================================================== > --- if_lem.c (revision 244673) > +++ if_lem.c (working copy) > @@ -32,6 +32,8 @@ > ******************************************************************************/ > /*$FreeBSD$*/ > > +#define MITIGATION > + > > gcooper> Could you please make MITIGATION into a proper compile time > flag via sys/conf/options with a more descript name? this is actually going away, with the code compiled in by default ... > @@ -281,6 +283,9 @@ > #define EM_TICKS_TO_USECS(ticks) ((1024 * (ticks) + 500) / 1000) > #define EM_USECS_TO_TICKS(usecs) ((1000 * (usecs) + 512) / 1024) > > +#define MAX_INTS_PER_SEC 8000 > +#define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) > + > > gcooper> Add parentheses around DEFAULT_ITR (I know the code was just > shuffled around, but thought I could ask :)..)? will do thanks luigi From owner-freebsd-emulation@FreeBSD.ORG Thu Dec 27 18:46:58 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2DE73D7D; Thu, 27 Dec 2012 18:46:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by mx1.freebsd.org (Postfix) with ESMTP id B683A8FC12; Thu, 27 Dec 2012 18:46:57 +0000 (UTC) Received: by mail-vb0-f44.google.com with SMTP id fc26so10295852vbb.3 for ; Thu, 27 Dec 2012 10:46:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TgKDM8NpNo0ZrfGlbYkVA97bdedyThROEb2EHJANCVk=; b=kUlApyeGB44dRvdckb9Rt9+wWTIRDdvhcWtThvsxYIp9BFoGvy67zxIYNp7L+qz7/j W6dz0aGgaXTl1lUC/5oKhpnw2DZ/W5SLeSU9jkCb73ybS0xpKtJ6vSHm1aWavLRCnnOE pYHyosUeVkE6KUv29DUUQwJk6cNGByW0NsBC17wQfbGik/0E9pB/XC/XbWLBvzAe7RPi ODFnr7YYnsHasASoyNn0B7W+CTun6iwXE0Hb9xJLkQ72En/vOo9yHmRA3hjekxKam+o6 hY6wiohf6N8AqBH4UvXh1gzQgda2N0fwiHiTcetz78d3fcRIxVhJaqxxQiwBr4LLU8CV eenA== MIME-Version: 1.0 Received: by 10.58.116.212 with SMTP id jy20mr48701085veb.5.1356634011440; Thu, 27 Dec 2012 10:46:51 -0800 (PST) Received: by 10.220.50.6 with HTTP; Thu, 27 Dec 2012 10:46:51 -0800 (PST) In-Reply-To: <20121227094649.GA48891@onelab2.iet.unipi.it> References: <20121227094649.GA48891@onelab2.iet.unipi.it> Date: Thu, 27 Dec 2012 10:46:51 -0800 Message-ID: Subject: Re: [RFC] proposed 'lem' patch to improve behaviour under emulation From: Jack Vogel To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: emulation@freebsd.org, current@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2012 18:46:58 -0000 LOL, it's ironic, my intention in creating lem was to isolate the old pre-PCIE driver from active changes so as to assure it's stability... but virtualization comes around to bit me in the butt :) I guess I'm agreeable in principle with what you're doing Luigi, but can you do me a favor and hold off until I'm technically back from vacation (after the new year) and let me review the code then? Thanks, Jack On Thu, Dec 27, 2012 at 1:46 AM, Luigi Rizzo wrote: > This patch implements two features for the 'lem' driver that > greatly improve the throughput under proper hypervisor. > This is joint work with Vincenzo Maffione and Giuseppe Lettieri, > I am posting it here for review, will then commit it > if there are no objections. > > The first change is to implement a sysctl to access the 'itr' > interrupt moderation register for the devices supported by this > driver. It is little more than adding a struct into the device > descriptor, and one line to create the dynamic sysctl entry, same > as it is done for the other mitigation registers. > > The second change is more interesting and has huge benefits on througput. > > Under virtualization, "VM exits" (which happen every time there is > an access to a register of the emulated peripheral) are extremely > expensive. In the tx path of the 'lem' driver, there is a write > to the TDT register on every packet sent. > > The patch we propose, if enabled through a sysctl (defaults off, > so no change from current behaviour) defers writes to the TDT > register when there is a pending transmit interrupt. > This means that, together with proper emulation of interrupt > mitigation on the hypervisor side, the number of VM exits > is dramatically reduced. To give you an idea, on a modern > system with qemu-kvm and companion patches, UDP throughput is > > KVM QEMU > standard KVM, standard driver 20 Kpps 6.3 Kpps > modified KVM, standard driver 37 Kpps 28 Kpps > modified KVM, modified driver 200 Kpps 34 Kpps > > As you can see, on kvm this change gives a 5x speedup to the tx path, > which combines nicely with the 2x speedup that comes from supporting > interrupt mitigation alone in the hypervisor. Without kvm (or kqemu ?) > the benefits are much lower, as the guest becomes too slow. > > Patch follows. It would be good if people with real hardware > using the 'lem' driver could test it to make sure it does no > harm on their devices (in any case the sysctl variable > dev.em.0.mit_enable must be set to explicitly enable it > at runtime). > > (for those curious to test it under kvm, i am also attaching a > patch that you need to apply to qemu in order to exploit the > effect of interrupt mitigation; it is a followup of a similar > patch i posted in july to the qemu mailing list, and i will > post it the update there as well, shortly. Unfortunately > we do not have kvm on freebsd..) > > cheers > luigi > From owner-freebsd-emulation@FreeBSD.ORG Fri Dec 28 02:52:34 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C55E2BEE; Fri, 28 Dec 2012 02:52:34 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1F1A38FC08; Fri, 28 Dec 2012 02:52:33 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id b47so5130704eek.31 for ; Thu, 27 Dec 2012 18:52:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=D+B8t/G9yrv3pGP9+FI5Fgv2qkKNx7/iW1c3bO3HcHc=; b=wYN0huLqREN1FrMGcw04cg26Ecl8UMSm5Uhj4txlEdyogpF/TOUalbQghx9dRIrYxZ bzYSEn3F96aTRCX3vAi+Pk2tw5WJ9zgD0HUIxaWMmH0N0zKcRcGQsXUx3Xn6Y7qcxQHM GoTa1A9nenx+p3wys/ntbzUx20ixKZJ0zVPsCmBoI6PwP0OtqwBI5+Se/oDEp1L3MKGg uTruzriYG3LiGYdba/EjogjVkRlk2JbV7zLBOtKj75396epVw99IRTFJYy+G7CtdQUXu okQghuqji8nHVJLE4tzcFvs6ncgZ5HYNIZbw69Gc8obdzh2B+EN+Yu0oyWTU1ZDNiQtX cp1Q== MIME-Version: 1.0 Received: by 10.14.209.193 with SMTP id s41mr82796817eeo.9.1356663146654; Thu, 27 Dec 2012 18:52:26 -0800 (PST) Sender: rizzo.unipi@gmail.com Received: by 10.14.0.2 with HTTP; Thu, 27 Dec 2012 18:52:26 -0800 (PST) In-Reply-To: References: <20121227094649.GA48891@onelab2.iet.unipi.it> Date: Thu, 27 Dec 2012 18:52:26 -0800 X-Google-Sender-Auth: br4Js-XI8P07j8_3uUuCIMRJeyA Message-ID: Subject: Re: [RFC] proposed 'lem' patch to improve behaviour under emulation From: Luigi Rizzo To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: emulation@freebsd.org, current@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2012 02:52:34 -0000 On Thu, Dec 27, 2012 at 10:46 AM, Jack Vogel wrote: > LOL, it's ironic, my intention in creating lem was to isolate the old > pre-PCIE driver from active changes so as to assure it's stability... > but virtualization comes around to bit me in the butt :) > > I guess I'm agreeable in principle with what you're doing Luigi, but > can you do me a favor and hold off until I'm technically back from > vacation (after the new year) and let me review the code then? > > sure, no rush -- i just wanted to have it out for review as it has been ready for a few weeks now. Regarding lem vs em i actually wonder if it wouldn't be better to consolidate the two drivers given the amount of common code. While i understand the desire for stability, i actually wonder if there is much if any leftover hw which uses 'lem' ... outside virtualization! cheers luigi From owner-freebsd-emulation@FreeBSD.ORG Fri Dec 28 06:07:24 2012 Return-Path: Delivered-To: emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 290BAD5E; Fri, 28 Dec 2012 06:07:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by mx1.freebsd.org (Postfix) with ESMTP id AFA078FC0A; Fri, 28 Dec 2012 06:07:23 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id p1so10323660vcq.24 for ; Thu, 27 Dec 2012 22:07:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=g31VcEatWqTYKhK99I7wVHcVP/kUJdqRn6JgWRe/hhw=; b=qHNNml4E1KaIl1u893+6r3cqpPyDLeCLwlX2wu8Ej39T6s/WHVtlK2C4gLKivgE5Vw 7DHYNCZE37IJ6pA6VNTjUzuHF87ZYhlSk9Ww52gAehgGPKQin53txCMMiD2sJMofd+M6 HiEshX1T+U21kVIWxl1ToU2ISqUFcIDE0yANgOr6BcDodgr8WGVP8b5elm+CQyphndrb RNDKElmb4xc3fsQKTQHWa62q+CN3jCB8DSK4mlF/equ0sIrc2ay9679zBWhTChAANpyt ATOLldeV6upVFY0AC7Z3MLV1TArYX1ALf2tlHXF0bFJMbbnrLm98DuA1v9yooWZ/kIio CFFw== MIME-Version: 1.0 Received: by 10.221.11.205 with SMTP id pf13mr49164827vcb.70.1356674837352; Thu, 27 Dec 2012 22:07:17 -0800 (PST) Received: by 10.220.50.6 with HTTP; Thu, 27 Dec 2012 22:07:17 -0800 (PST) In-Reply-To: References: <20121227094649.GA48891@onelab2.iet.unipi.it> Date: Thu, 27 Dec 2012 22:07:17 -0800 Message-ID: Subject: Re: [RFC] proposed 'lem' patch to improve behaviour under emulation From: Jack Vogel To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: emulation@freebsd.org, current@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2012 06:07:24 -0000 I don't know, in some ways it might be more interesting to make something just for a virtualized device, however reality is that I have way too many higher priority items to worry about after the new year gets underway than that, even so, we can see... Jack On Thu, Dec 27, 2012 at 6:52 PM, Luigi Rizzo wrote: > On Thu, Dec 27, 2012 at 10:46 AM, Jack Vogel wrote: > >> LOL, it's ironic, my intention in creating lem was to isolate the old >> pre-PCIE driver from active changes so as to assure it's stability... >> but virtualization comes around to bit me in the butt :) >> >> I guess I'm agreeable in principle with what you're doing Luigi, but >> can you do me a favor and hold off until I'm technically back from >> vacation (after the new year) and let me review the code then? >> >> > sure, no rush -- i just wanted to have it out for review as it has been > ready for a few weeks now. > > Regarding lem vs em i actually wonder if it wouldn't be better to > consolidate the two drivers given the amount of common code. > While i understand the desire for stability, i actually wonder if there > is much if any leftover hw which uses 'lem' ... outside virtualization! > > cheers > luigi > > From owner-freebsd-emulation@FreeBSD.ORG Sat Dec 29 05:42:04 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B3E02A3; Sat, 29 Dec 2012 05:42:04 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by mx1.freebsd.org (Postfix) with ESMTP id 9764E8FC13; Sat, 29 Dec 2012 05:42:03 +0000 (UTC) Received: by mail-vb0-f51.google.com with SMTP id fq11so11153580vbb.24 for ; Fri, 28 Dec 2012 21:42:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HDUNRTTTSt2u2koyCu53hp8PAqf/l0bKT2VH/z8RwxQ=; b=yIdEA6c0E5j6z+rco2ld/zPQxJrxn7NjCm3cjYQVWDyijLhZcVNPheEYKloXD1D8f1 bQBQtQOY5HrWpSUfj/0QCrj6hr3sMjq9IOtIBUlPGCZydcJT6MEvgTsDxhUQ9fijG6tL O1AO9SbeXXeshm0xQUphnYCR5Mu5mgRkkZP7zV5VhGpjFXdaAOz7RBxobigmNVnUbTGl 51jUaLwlqiYwTz0GiVGtk7MDdhYYQ15UwLYs8DZYN+SYMTK70Q0SbQninyMylMi2b1kN jt7IPScoIp7a6/ZkHLlxzCIWHHDs3gSwPyrqSLrj3l/7ORiOXokaD6b6LvJR/hVIOzua bHDQ== MIME-Version: 1.0 Received: by 10.52.35.37 with SMTP id e5mr46769939vdj.115.1356759722484; Fri, 28 Dec 2012 21:42:02 -0800 (PST) Received: by 10.220.148.147 with HTTP; Fri, 28 Dec 2012 21:42:02 -0800 (PST) Received: by 10.220.148.147 with HTTP; Fri, 28 Dec 2012 21:42:02 -0800 (PST) In-Reply-To: <20121226082755.ee1d4a3077742aa0ff1638e2@gmx.net> References: <201212241227.15165.naylor.b.david@gmail.com> <20121226082755.ee1d4a3077742aa0ff1638e2@gmx.net> Date: Sat, 29 Dec 2012 07:42:02 +0200 Message-ID: Subject: Re: Wine-fbsd64 updated to 1.5.20 (32bit Wine for 64bit FreeBSD) From: David Naylor To: Jens Jahnke Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-emulation@freebsd.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2012 05:42:04 -0000 On 26 Dec 2012 9:28 AM, "Jens Jahnke" wrote: > > Hi, Hi, > On Mon, 24 Dec 2012 12:27:11 +0200 > David Naylor wrote: > > DN> Since it is possible to install the existing pkg > DN> packages in a pkgng environment (which I do) this is not a high > DN> priority. > > is there a documentation for that? I searched the pkgng docs but found > nothing regarding installation of "old" packages or converting them to > a newer version. Use the old `pkg_ng` command to install the package. As long as the files installed with the old and the new package tools are mutually exclusive you shouldn't have a problem. If you patch your ports tree with the wine-fbsd64 diff then it is possible to use `pkg2ng` to convert to the pkgng format. (Although I have never tested that, see documentation for pkg2ng and `pkg create`). Regards