From owner-freebsd-current@FreeBSD.ORG Fri Oct 3 00:50:58 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A3D1FA9; Fri, 3 Oct 2014 00:50:58 +0000 (UTC) Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailuogwprd01.lss.emc.com", Issuer "RSA Corporate Server CA v2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 260F0AFF; Fri, 3 Oct 2014 00:50:57 +0000 (UTC) Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s930omWm032148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Oct 2014 20:50:49 -0400 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s930omWm032148 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1412297449; bh=22QYeLWUhxVH4tZsDtpodUqW+Kw=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=NZyGhX2aI/w5wCsOsSMKi4uIZ5rE/cA1iS1YZMi4kQ3KcY3n96kCnRbjrvdKZzEq9 KSgp1QYuSFHY6xJIdizTrow+71TbC+7rdja0Wzk33J+0YuZ0C5tSe8NKvXsW+S0zzI YdoHNNYBlqixg4OXi6EaICAacOB0Xa6SLhHt/dvE= X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s930omWm032148 Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd02.lss.emc.com (RSA Interceptor); Thu, 2 Oct 2014 20:50:16 -0400 Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s930oWwB028280 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Oct 2014 20:50:32 -0400 Received: from mx34a.corp.emc.com ([169.254.1.46]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Thu, 2 Oct 2014 20:50:32 -0400 From: "O'Connor, Daniel" To: "O'Connor, Daniel" Date: Thu, 2 Oct 2014 20:50:30 -0400 Subject: Re: What do you use for kernel debugging? Thread-Topic: What do you use for kernel debugging? Thread-Index: Ac/epAhuw8pAITpYSzukJWAVWy1m9Q== Message-ID: <18C885A5-5162-4868-8A1A-DDBC7A92CCF5@emc.com> References: <20140928071641.M7664@beckpeccoz.com> <20140929003358.M78145@aoek.com> <542AC1C8.9030101@freebsd.org> <90CE0701-F1CB-41DF-B3D2-87816DC03DF9@emc.com> <3718AED6-9514-49F9-AF11-B47CFAF01161@emc.com> In-Reply-To: <3718AED6-9514-49F9-AF11-B47CFAF01161@emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com X-RSA-Classifications: DLP to NYP, DLM_1, public X-Mailman-Approved-At: Fri, 03 Oct 2014 01:14:40 +0000 Cc: Adrian Chadd , =?Windows-1252?Q?Jos=E9_P=E9rez_Arauzo?= , FreeBSD Current , Benjamin Kaduk , Garrett Cooper X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 00:50:58 -0000 On 1 Oct 2014, at 15:54, O'Connor, Daniel wrote: > On 1 Oct 2014, at 14:33, Adrian Chadd wrote: >> There's also something for XHCI. >=20 > So I see.. >=20 > Section 7.6 in here has details.. > http://www.intel.com.au/content/dam/www/public/us/en/documents/technical-= specifications/extensible-host-controler-interface-usb-xhci.pdf >=20 > Interestingly unlike the EHCI version it does not require hardware betwee= n the debugger and debugee, only a special cable. (see http://msdn.microsof= t.com/en-us/library/windows/hardware/hh439372(v=3Dvs.85).aspx) I wrote a quick program to dump xHCI extended capabilities https://gist.git= hub.com/DanielO/c42819ae69a1f680039a Run pciconf -lb and look for the base value for xhciX then run the command = with that like so.. xhci0@pci0:3:0:0: class=3D0x0c0330 card=3D0x077815ad chip=3D0x077815ad rev= =3D0x00 hdr=3D0x00 bar [10] =3D type Memory, range 64, base 0xfd4c0000, size 131072, ena= bled root@foo:~ # ./xhcicap 0xfd4c0000 HCCPARAMS1 =3D> 0x0388f283 xECP (0xfd4c0e20) =3D> ID 2 (Supported protocol) Specific 0x0300 xECP (0xfd4c0e23) =3D> ID 3 (Extended PM) Specific 0x4253 (this is a VMWare Fusion guest with USB3 enabled) I ran it on Gigabyte Z77-D3H board (only real hardware I had handy with USB= 3) which has 2 USB3 controllers - one on the Intel chipset, the other an Et= ron EJ168. It shows.. Intel.. HCCPARAMS1 =3D> 0x20007181 xECP (0xf7f08000) =3D> ID 2 (Supported protocol) Specific 0x200 xECP (0xf7f08008) =3D> ID 1 (Legacy support) Specific 0x3001 Etron.. HCCPARAMS1 =3D> 0x040050af xECP (0xf7c01000) =3D> ID 1 (Legacy support) Specific 0x0000 Neither support debugging (and according to the spec the later is broken as= it is supposed to have at least one =91supported protocol=92 entry). Regards, Daniel O=92Connor Senior Software Engineer Isilon Platforms Team