From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 26 10:09:08 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C097416A419 for ; Sat, 26 Jan 2008 10:09:08 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D082613C4CE; Sat, 26 Jan 2008 10:09:03 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <479B06BC.7030603@FreeBSD.org> Date: Sat, 26 Jan 2008 11:09:00 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Joseph Koshy References: <4795CC13.7080601@moneybookers.com> <868x2i3v8d.fsf@ds4.des.no> <864pd63v2h.fsf@ds4.des.no> <4795FE54.9090606@moneybookers.com> <86lk6i0vzk.fsf@ds4.des.no> <479605E2.6070709@moneybookers.com> <479621BE.2060907@FreeBSD.org> <4796357B.9020508@moneybookers.com> <47963911.4000002@FreeBSD.org> <84dead720801252234v1e7a8856g339faa02c1250bbf@mail.gmail.com> In-Reply-To: <84dead720801252234v1e7a8856g339faa02c1250bbf@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?Erling_Sm=F8rgrav?= , =?ISO-8859-1?Q?Dag-?=, freebsd-hackers@freebsd.org, Stefan Lambrev Subject: Re: gettimeofday() in hping X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2008 10:09:08 -0000 Joseph Koshy wrote: >> OK, this is the famous problem with modern CPUs that jkoshy has declined >> to work around :( There are patches for this in perforce, see >> >> http://perforce.freebsd.org/changeView.cgi?CH=126189 > > "Famous problem" indeed :). I declined the patch because it > is incorrect and incomplete. > I will accept a patch that demonstrates clue about the > workings of the overall system---the changes in the patch > should be safe, complete, should demonstrate that the submitter > has read and understood vendor documentation, should preserve > user experience for naming events, and each supported PMC event > needs to be documented in pmc.3. I am aware of these issues but repeat my statement that the lack of working pmc on modern CPUs is causing serious difficulties for our developer and user base, as witnessed again in this thread. Kris