From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:37:25 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E30E1065674; Tue, 7 Aug 2012 23:37:25 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1F78FC0C; Tue, 7 Aug 2012 23:37:24 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so224334vcb.13 for ; Tue, 07 Aug 2012 16:37:24 -0700 (PDT) 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=un6fDh/QTrYotz1oP5H9ta4Nva0r8xEtSZxTBW2kIaU=; b=GkGamzaUH7jPD8w3rcLuPs7iyWjQf/3nmzI9K9AGb8lGmW+pThjZfJvrFYritMXoAf Loc9XZCYWvguSRdvmvdOQFY40DSmAtgo5s5UjIN7thaNdO3e/bv/ClFJClxBAmWEqlDi SltyZqq1WTpRMFXDdDTK+x81Fl5FT/XG50oil0pu/UAh2qz0xA74ZwhHM76Zx747Ajr9 b+nN/nAoSPoBMH5ZOC/ShBXzDAKJEWEsnkG6MUZZOBm++mc0MY8Eh8EHlBIToxDWAoiI yrk5GEN9q0VgcxIWUj74OY6ArG9ihP+/I/tXyP0z+KlR3VInGPLGHnh9/eXvAq1G0Bv+ onhA== MIME-Version: 1.0 Received: by 10.221.10.13 with SMTP id oy13mr350640vcb.14.1344382644298; Tue, 07 Aug 2012 16:37:24 -0700 (PDT) Received: by 10.58.114.102 with HTTP; Tue, 7 Aug 2012 16:37:24 -0700 (PDT) In-Reply-To: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> References: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> Date: Tue, 7 Aug 2012 19:37:24 -0400 Message-ID: From: Ryan Stone To: sbruno@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-hackers@freebsd.org" Subject: Re: pmc warnings on stable/9 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: Tue, 07 Aug 2012 23:37:25 -0000 On Tue, Aug 7, 2012 at 7:16 PM, Sean Bruno wrote: > I have no idea the significance, or danger. When compiling on stable/9 > I have always seen the following WARNINGS. Can we silence/fix these? > Or is it supposed to be that way? :-) > > WARNING: hwpmc_soft.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_pmc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_rwlock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_sx.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_lock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_intel.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_tsc.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_amd.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_clock.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: kern_mutex.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: trap.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_x86.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_uncore.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_piv.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_core.c: enum pmc_event has too many values: 1531 > 1023 > WARNING: hwpmc_logging.c: enum pmc_event has too many values: 1531 > > 1023 > WARNING: hwpmc_mod.c: enum pmc_event has too many values: 1531 > 1023 > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" These warnings(and the previous one from your other thread) both come from ctfconvert. I haven't looked into them in detail but I suspect that the CTF format is not able to represent things like enums with more than 1024 entries, or structures with more than a certain number of members. I've never seen any actual side-effects of the warnings, although I suspect that if you tried to use DTrace to examine variables with the affected types you wouldn't be able to inspect everything. As far as I know, DTrace is the only consumer of CTF data in the kernel. I have dreams of replacing DTrace's usage of CTF with libdwarf, but that's little more than idle musings on my part at this stage.