From: "Vitaly Zdanevich" <zdanevich.vitaly@ya.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sys-apps/corefreq/
Date: Fri, 2 Jun 2023 05:15:08 +0000 (UTC) [thread overview]
Message-ID: <1685682893.7a0864d7cdd49d0f9ab45248bfd28af2518551b9.zdanevich.vitaly@gentoo> (raw)
commit: 7a0864d7cdd49d0f9ab45248bfd28af2518551b9
Author: Vitaly Zdanevich <zdanevich.vitaly <AT> ya <DOT> ru>
AuthorDate: Fri Jun 2 05:14:53 2023 +0000
Commit: Vitaly Zdanevich <zdanevich.vitaly <AT> ya <DOT> ru>
CommitDate: Fri Jun 2 05:14:53 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=7a0864d7
sys-apps/corefreq: longdescription add
Signed-off-by: Vitaly Zdanevich <zdanevich.vitaly <AT> ya.ru>
sys-apps/corefreq/metadata.xml | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/sys-apps/corefreq/metadata.xml b/sys-apps/corefreq/metadata.xml
index 1184002b6..e0411fbbb 100644
--- a/sys-apps/corefreq/metadata.xml
+++ b/sys-apps/corefreq/metadata.xml
@@ -6,4 +6,25 @@
<email>zdanevich.vitaly@ya.ru</email>
<name>Vitaly Zdanevich</name>
</maintainer>
+ <longdescription lang="en">
+CoreFreq provides a framework to retrieve CPU data with a high degree of precision:
+
+* Core frequencies and ratios; SpeedStep (EIST), Turbo Boost, Hyper-Threading (HTT) and Base Clock
+* Performance counters including Time Stamp Counter (TSC), Unhalted Core Cycles (UCC), Unhalted Reference Cycles (URC)
+* Number of instructions per cycle or second, IPS, IPC, or CPI
+* CPU C-States C0 C1 C3 C6 C7 - C1E - Auto/UnDemotion of C1 C3
+* DTS Temperature and Tjunction Max, Thermal Monitoring TM1 TM2 state, Vcore
+* Topology map including Caches for boostrap and application CPU
+* Processor features, brand and architecture strings
+* In progress: Uncore, Memory Controller channels and geometry, DIMM timings,
+* Stress tools, Power and Energy (RAPL, P-State, HWP, TDP), Overclocking, cpuidle and cpufreq driver, ClockSource, Mitigation Mechanisms
+
+To reach this goal, CoreFreq implements a Linux Kernel module which employs the followings:
+
+* asm code to keep as near as possible the readings of the performance counters;
+* per-CPU, implements slab data memory and high-resolution timer;
+* compliant with suspend / resume and CPU Hot-Plug;
+* a shared memory to protect kernel from the user-space part of the software;
+* atomic synchronization of threads to avoid mutexes and deadlock
+ </longdescription>
</pkgmetadata>
next reply other threads:[~2023-06-02 5:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 5:15 Vitaly Zdanevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-02 23:01 [gentoo-commits] repo/proj/guru:dev commit in: sys-apps/corefreq/ Vitaly Zdanevich
2024-03-02 1:14 Vitaly Zdanevich
2024-02-27 20:28 Vitaly Zdanevich
2024-02-27 20:26 Vitaly Zdanevich
2023-09-15 9:33 Vitaly Zdanevich
2023-09-14 5:53 Vitaly Zdanevich
2023-06-07 5:40 Vitaly Zdanevich
2023-06-01 5:34 Vitaly Zdanevich
2023-06-01 5:22 Vitaly Zdanevich
2023-05-31 5:58 Vitaly Zdanevich
2023-05-31 5:57 Vitaly Zdanevich
2023-05-31 5:32 Vitaly Zdanevich
2023-05-30 12:53 Vitaly Zdanevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1685682893.7a0864d7cdd49d0f9ab45248bfd28af2518551b9.zdanevich.vitaly@gentoo \
--to=zdanevich.vitaly@ya.ru \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox