From owner-freebsd-arch@freebsd.org Wed Nov 8 06:37:54 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3847E6F57A for ; Wed, 8 Nov 2017 06:37:54 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B89B6CFE9 for ; Wed, 8 Nov 2017 06:37:53 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Received: from sc1.bsdpad.com ([163.172.212.18]:27963) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (LOGIN:rb743) (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1eCJzj-0002sI-n2 (Exim 4.89) for freebsd-arch@freebsd.org (return-path ); Wed, 08 Nov 2017 06:37:51 +0000 Date: Wed, 8 Nov 2017 06:31:09 +0000 From: Ruslan Bukin To: freebsd-arch@freebsd.org Subject: Intel PT support Message-ID: <20171108063109.GA68007@bsdpad.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) Sender: "R. Bukin" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2017 06:37:54 -0000 Hi, Here is patch enables Intel Processor Tracing (PT) support. This is exciting new and first(?) hardware-level tracing support available for FreeBSD! PT is supported on Intel 5th generation Core (Broadwell), 6th generation Core (Skylake) CPUs, and later. I'm testing it currently on a late Kabylake. PT is evolving since its introduction in Broadwell CPU and I'm not sure if the features we use on Kabylake are available on Broeadwell (tracing to SG buffer for example). I will try to support all of these CPUs but if someone can help testing it would be good. Providing the output of pt_enumerate() on your CPU may be helpful as well. So with a minimal impact on system perfomance we can trace pretty much everything now. I provided simple 'pmctrace' application that enables tracing and decodes tracing buffers. It supports function tracing. Intel PT provides 25 types of packets, we currently decode few of them only. Example usage: 1. Trace all the conditional branches for uname(1) application. pmctrace -u pt,branches uname 2. Trace all the conditional branches in memset(3) function in libc. pmctrace -u pt,branches -i libc.so.7 -f memset sleep 1 3. Trace all the conditional branches for copyin() and show timestamp (TSC -- amount of clock cycles since boot). sudo pmctrace -s pt,branches,tsc -i kernel -f copyin So I have added new counters modes for HWPMC: MODE_ST - system tracing MODE_TT - virtual thread tracing We may look for ARM tracing technologies later as well. It is on review here: https://reviews.freebsd.org/D12875 It require libipt decoder from Intel as well: https://reviews.freebsd.org/D12717 Thanks. Ruslan From owner-freebsd-arch@freebsd.org Thu Nov 9 15:14:36 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C54DE531BC for ; Thu, 9 Nov 2017 15:14:36 +0000 (UTC) (envelope-from jessica.mock@leadsopportunities.com) Received: from ded3096.inmotionhosting.com (server.leadsopportunities.com [173.247.254.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 197406A72B for ; Thu, 9 Nov 2017 15:14:36 +0000 (UTC) (envelope-from jessica.mock@leadsopportunities.com) Received: from [106.51.20.159] (port=41868 helo=SaadPC) by ded3096.inmotionhosting.com with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1eCoXL-00012D-Eb for freebsd-arch@freebsd.org; Thu, 09 Nov 2017 07:14:35 -0800 From: "jessica mock" To: Subject: Perforce Users Date: Thu, 9 Nov 2017 09:14:23 -0600 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdNZbWs/jd7y+Ac5T/+GdqSSkmtQNg== Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ded3096.inmotionhosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - leadsopportunities.com X-Get-Message-Sender-Via: ded3096.inmotionhosting.com: authenticated_id: jessica.mock@leadsopportunities.com X-Authenticated-Sender: ded3096.inmotionhosting.com: jessica.mock@leadsopportunities.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2017 15:14:36 -0000 Hi, Would you be interested in acquiring Perforce Users for your lead generation, email campaign, tele-calling, product promotion activities across the globe? We provide IT and other Decision Makers contacts that use Perforce. Let me know if you are interested and we can connect to discuss on this. Await your response! Thanks, Jessica Mock Marketing Executive | List acquisition | Technology Lists | Email/Data Appending | Search Engine Optimization | If you don't want to include yourself in our mailing list, please reply back "RE: Leave Out" in a subject line From owner-freebsd-arch@freebsd.org Sat Nov 11 22:50:45 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE060E4E76D for ; Sat, 11 Nov 2017 22:50:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A925871943 for ; Sat, 11 Nov 2017 22:50:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id A5AA3E4E769; Sat, 11 Nov 2017 22:50:45 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A53D7E4E767 for ; Sat, 11 Nov 2017 22:50:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B32171940 for ; Sat, 11 Nov 2017 22:50:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x232.google.com with SMTP id p186so17036885ioe.12 for ; Sat, 11 Nov 2017 14:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=YtHKfVf8JnJ3MAWwK//k3hXx0fgIEWYiMbvDnoM5nGw=; b=rG7SD/IXDSp1gUl0ij7F6o2xD1t5qbg1iBAKLgbm27h26+neT2OxhcLaxVUr2vjGpd 6IFE2k8/dzA/BExIFKTBpWsT0UK9+N2jtSSgfNYvcsZuwhkZWcabl9LGibOFwpNv2uGa wSCTrgwbFPibmG4erafhYVef3t2geqoazsgCeid7CaWNfo0jxNO4ra+H3++bLNMvZ4kQ 2XqA2WboWZ88DOJrXm3MyxJVRwBg3j8HFrCSxYnzcOYTZl22WKFkDzZYLTP6i7UZGWdk zAfbgShRYeeYZaypXnr/7W+dhMbZCHJdRyrNCYlg9j8WQo+wwI3kzCne7YRAPFk+/pee koBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=YtHKfVf8JnJ3MAWwK//k3hXx0fgIEWYiMbvDnoM5nGw=; b=Q7+NP7W4ORRH+hG54n0QkUj7dQZZP290VwOKips/349gOLuAvwursDpxreYypJVALf Rtn+GmWBvG31HQ98FAril3Q/nSlhpT9JnCV07k1oxTy/wDRncTHop3y5nlsZIcAdt6DW f8YfcqyPmP79sTLeq8s308DzixQIMUVU3dpg2Gq+Z8zrJ5vPZR7++FkBSkeUqM2s50uy kzI8q4rB+q9Nn8iFV4BMbiBW/7vsKptWkA98l58XmipgMeVdfagheFx1NhrWQIjiIFjK zJtn2EJTFJLGiklKfjAbpwOyZrLVpC/W+0RYs9f3m7SWy/AFPlDjnSB3lB8HQroEZCgv XCDg== X-Gm-Message-State: AJaThX5YxRqXa5tZOQbHlTca+ST72Q4djNy7Du8xHnerKC2mGn7DHl6I l5/Y4o/8mhpD+LuJ0sO1FLa2gAYc/5vBAh1PqP5CXQ== X-Google-Smtp-Source: AGs4zMYVdTa/KI3Xkt6IepSD2wcJk1zZWirNj8PGzpBtx1wT71+85r3Fi17v8KRK7ZUjoF9p7VjYIedmI3La2gqV0FE= X-Received: by 10.107.81.21 with SMTP id f21mr5130916iob.63.1510440644159; Sat, 11 Nov 2017 14:50:44 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Sat, 11 Nov 2017 14:50:43 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:5122:5997:63f8:a0df] From: Warner Losh Date: Sat, 11 Nov 2017 15:50:43 -0700 X-Google-Sender-Auth: 6fpqgNrObMmp0kK8x47kEHYQzJ0 Message-ID: Subject: Coming move of files (src/sys/boot/fdt/dts -> src/sys/dts and then src/sys/boot -> src/stand) To: "freebsd-arch@freebsd.org" , "freebsd-embedded@freebsd.org" , Ed Maste Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2017 22:50:45 -0000 Greetings, The subject line says it all... I plan on moving src/sys/boot to src/stand since it isn't part of the kernel (though it uses parts of the kernel, like user land uses parts of the kernel). It's built with buildworld, and more properly belongs there, but none of the existing top-level directories fit the bill. There's one exception, however. sys/boot/fdt/dts contains the DTS sources for a bunch of embedded boards. This needs to remain in the kernel because some kernels attach DTS files statically to the final image. I propose this land in src/sys/dts. Of course, all references to the old paths will be migrated to new paths. I'd expect to move this before we import lua boot, and that lua would thus wind up in src/contrib. Comments? Warner