From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 7 23:52:50 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 3A9B3106564A; Tue, 7 Aug 2012 23:52:50 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 934298FC0A; Tue, 7 Aug 2012 23:52:49 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so143205wgb.31 for ; Tue, 07 Aug 2012 16:52:48 -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=J6v4ZmgB4Zn7P/JEpMKTnb+oLssm8RDJ5Dnp/yhHL4A=; b=UOU3kDcBozQc0LO+sANsQJCc6B0bokMsV++OkrOGLG/UlQbzkEeX2fM8cdranUL4DJ Lsyas1uCe1/Q9tumkptZ19x5+JbSyR0gwb5f/z1xz9AbxKVDPRo3/Gx6pZ18Z5WdcwfO pT01CgCBlAQuEnku2L0vxuhjjdqM4nzVaoTYZ+B53NtF4eE2vJoRqDXqHnUl2ACGWFXj 0IbpU+KJgUPGU4SVxMHM1izg+DiLZGTWSs+k0PNJm9XSZhAybjMjx982CKlywy3oebLQ C1RKO0GrkpsA/mUcw5cYh/vyR4bdHXQdKrhwqb4Dk/t81u/2ohvdWJN7oFbt7NFcoiuH cR7A== MIME-Version: 1.0 Received: by 10.216.232.204 with SMTP id n54mr9009823weq.182.1344383568445; Tue, 07 Aug 2012 16:52:48 -0700 (PDT) Received: by 10.216.241.203 with HTTP; Tue, 7 Aug 2012 16:52:48 -0700 (PDT) In-Reply-To: References: <1344381411.18854.16.camel@powernoodle.corp.yahoo.com> Date: Tue, 7 Aug 2012 16:52:48 -0700 Message-ID: From: Jim Harris To: Ryan Stone 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:52:50 -0000 On Tue, Aug 7, 2012 at 4:37 PM, Ryan Stone wrote: > 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. > _______________________________________________ > 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" FYI - r207578 added this warning to FreeBSD's ctf, specifically to handle the large pmc_entry enumeration. http://svnweb.freebsd.org/base?view=revision&revision=207578