[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#990124: marked as done (unblock: libpfm4/4.11.1+git32-gd0b85fb-1)



Your message dated Mon, 21 Jun 2021 18:52:56 +0000
with message-id <E1lvP2W-0007Nh-42@respighi.debian.org>
and subject line unblock libpfm4
has caused the Debian Bug report #990124,
regarding unblock: libpfm4/4.11.1+git32-gd0b85fb-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
990124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990124
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package libpfm4

I'd like to update libpfm4 to a new snapshot for adding/improving support
for modern CPUs (e.g. Zen2/3) and fixing some encoding issues (e.g. current
kernels may issue a warning if some unused (or rather kernel private)
bits in the structs are not cleared).

The diffstat looks huge at a first glance: 2137 insertions(+), 97 deletions(-)
but 1750 added lines alone are for newly added files (and tests) to
support new CPUs and their events and therefore have a very low regression
potential (it can hardly get worse than not supporting some chips/events).


Added files:
 docs/man3/libpfm_amd64_fam19h_zen3.3     |   49 +
 docs/man3/libpfm_amd64_fam19h_zen3_l3.3  |   19
 docs/man3/libpfm_intel_icx.3             |   84 ++
 lib/events/amd64_events_fam19h_zen3.h    |  999 +++++++++++++++++++++++++++++++
 lib/events/amd64_events_fam19h_zen3_l3.h |   55 +
 lib/pfmlib_amd64_fam19h.c                |   56 +
 lib/pfmlib_amd64_fam19h_l3.c             |   76 ++
 lib/pfmlib_amd64_rapl.c                  |  121 +++
Modified files:
 README                                   |    1
 debian/changelog                         |    9
 docs/Makefile                            |    4
 docs/man3/libpfm_arm_a64fx.3             |    4
 docs/man3/libpfm_intel_icl.3             |    2
 docs/man3/pfm_get_os_event_encoding.3    |   16
 include/perfmon/perf_event.h             |    1
 include/perfmon/pfmlib.h                 |    7
 lib/Makefile                             |    7
 lib/events/arm_neoverse_n1_events.h      |   20
 lib/events/intel_icl_events.h            |   55 +
 lib/events/intel_skl_events.h            |    2
 lib/events/perf_events.h                 |   30
 lib/pfmlib_amd64.c                       |   62 -
 lib/pfmlib_amd64_fam11h.c                |    2
 lib/pfmlib_amd64_fam12h.c                |    2
 lib/pfmlib_amd64_fam15h.c                |    2
 lib/pfmlib_amd64_fam16h.c                |    2
 lib/pfmlib_amd64_fam17h.c                |    2
 lib/pfmlib_amd64_perf_event.c            |   20
 lib/pfmlib_amd64_priv.h                  |   33 -
 lib/pfmlib_arm_armv8.c                   |    2
 lib/pfmlib_common.c                      |    4
 lib/pfmlib_intel_icl.c                   |   44 +
 lib/pfmlib_intel_nhm_unc.c               |    2
 lib/pfmlib_intel_snbep_unc.c             |    4
 lib/pfmlib_intel_x86_perf_event.c        |   16
 lib/pfmlib_perf_event.c                  |    2
 lib/pfmlib_perf_event_pmu.c              |    4
 lib/pfmlib_priv.h                        |    4
 lib/pfmlib_s390x_perf_event.c            |   56 +
 perf_examples/notify_group.c             |    2
 perf_examples/perf_util.c                |    8
 tests/validate_x86.c                     |  344 ++++++++++
 42 files changed, 2137 insertions(+), 97 deletions(-)

Andreas

unblock libpfm4/4.11.1+git32-gd0b85fb-1

Attachment: libpfm4_4.11.1+git32-gd0b85fb-1.dsc.diff.xz
Description: application/xz


--- End Message ---
--- Begin Message ---
Unblocked.

--- End Message ---

Reply to: