cyring / xfreq Goto Github PK

This is a question whether XFreq should be refactored to integrate the CoreFreq kernel module ?

• Benefits

1. accuracy of the driver
2. more processors and their technologies, features, capabilities support (Ryzen, Xeon), Overclocking, Uncore
3. more data coming from the PCI space: IMC, DRAM, Bus
4. getting Kernel data with less overhead, such as monitoring the tasks list

• Cons

1. CoreFreq needs Kernel mode whereas XFreq is a userspace software (with the help of standard kmods)
2. FreeBSD CoreFreq driver is not developed
3. impacts the CoreFreq daemon to manage multi-clients:
   • process synchronization,
   • shared memory strategy,
   • commands ring-buffers,
     ...

Web Socket should send Metadata during the JSON stage 0, such as :

"Metadata": {
    "TSC": "Time Stamp Counter",
    "HTT": "Hyper-Threading",
    "C3A": "C3 Auto Demotion"
}

Perhaps, add attributes per variable :

{
    "min": 000,
    "max": 999,
    "thresholds": [ 25, 37.2, 39.9 ]
}

In the main widget, press enter to submit a command: the GUI exits with a violation access.
It shouldn't be difficult to fix but I'm focusing on CoreFreq project.

This is impacts &A.configFile and &A.Geometries in main() and LoadSettings()

What steps will reproduce the problem?

1. Run xfreq-intel
2. Run xfreq-gui
3. Invalid values found in the System Information Widget

What is the expected output?
Same Channels and Timings values as those found with Linux

Revise some fDraw() calls with BuildLayout() when MapLayout() and FlushLayout() are not required.

AT&T inline codes are wrong

On a fresh git checkout:
commit 4a95bc4
Author: CyrIng [email protected]
Date: Fri Dec 1 13:35:07 2017 +0100

Update LICENSE.

On:
$ cat /etc/issue
Ubuntu 16.04.3 LTS \n \l

Using the tiling window manager:
$ i3 --version
i3 version 4.11 (2015-09-30, branch "4.11") © 2009 Michael Stapelberg and contributors

After loading the msr module and running the gui with the i3, I momentarily see a corner of what looks like it might be a splash screen, and then the program exits. I tried a few command line parameters to try to disable the splash screen, but it's likely I got the whole "type a hex value as a command line parameter" thing wrong. It is not uncommon for programs that expect to control their own window size to fail on tiling window managers where that assumption does not hold; maybe this is something along those lines.

I don't have time to help or evaluate this further at the moment; just wanted to share back the info. Thanks!

What steps will reproduce the problem?

1. Using a processor with the Fast-Strings feature is not available
2. Check its value in the SysInfo Widget

What is the expected output? What do you see instead?

• Expected: Fast-Strings reported as not available in CPUID and disable in the MSR register.
• Instead: Fast-Strings reported as not available in CPUID but enabled in MSR.

'''
outl(int fd, unsigned int addr, unsigned int val)
{
struct iodev_pio_req out={.access=IODEV_PIO_READ
'''

IODEV_PIO_WRITE instead of IODEV_PIO_READ

1. HTML5 compliant code with header, footer and so on.
2. CSS 3 based menu which provides
   • a horizontal bar for the running windows;
   • a vertical bar for the launcher, the settings, and the contextual menu.
3. Add a footer with a tab-list of Web Socket servers.
4. Transmit the SmBIOS data, the memory controller settings, the kernel information.
5. Add the SysInfo Widget.
6. Add a versatile window, with a [Close] button and a listbox, to display the following categories :
   • Factory and fixed values (@ JSON stage 0);
   • Dictionary data ( Metadata @ JSON stage 0);
   • Help and instructions.
7. The Settings menu will link to :
   • a dialog box with a color wheel and a listbox of the UI items;
   • a dialog box to save and load the user preferences;
   • a theme selector. (split the CSS between the menu and the colors skin)
8. Provide three kinds of drawing :
   • 2D canvas;
   • 3D Web GL;
   • HTML only.
9. Splash the XFreq logo at startup, during the JSON stage 0 (at least 1 second).
10. Change the windows movement, from Drag & Drop to a full javascript event script.
11. Without multithreading, do any computation between two transmission ticks.
12. As xfreq-gui, maybe provide commands to alter the operational execution of the processor, if security is not a issue.
13. Reimplemente the Web Socket server with Node.js :
    • to benefit a long terme support.
    • what about the 64 bits registers in Node.js ?
14. User agent detection to switch to mobile version.
15. Collect and transmit the mounted file systems data.
16. Port to the ARM Raspberry Pi, and thus to mobile devices.

Remove any Turbo MSR read if the processor is a Core2