https://bugs.kde.org/show_bug.cgi?id=500745

--- Comment #5 from John <ilikef...@waterisgone.com> ---
(In reply to TraceyC from comment #3)
> I verified on git-master that the "Processors" string in About this System
> shows the CPU as described
> On my laptop:
> Processors: 8 x AMD Ryzen 7 3700U....
>
> Also, in the CPU page of Info Center - which appears to use data from lscpu
> CPU(s): 8
>
> This is coming from the OS. On my system:
> /proc/cpuinfo shows 8 "processors"
> lscpu shows CPU(s): 8
>
> The confusion seems to stem from the assumption that About this System is
> showing the physically installed hardware, rather than the logical
> information from the OS. This is understandable, given how the text reads.
Your CPU seems to have 4 cores and 8 threads:
https://www.techpowerup.com/cpu-specs/ryzen-7-3700u.c2140
Exactly as mine (in this bug report):
https://www.techpowerup.com/cpu-specs/core-i5-8250u.c1972
Great that you figured out from where the CPU details page takes its data from!
Running lscpu from the terminal shows:
CPU(s):                   8
  On-line CPU(s) list:    0-7
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    CPU family:           6
    Model:                142
    Thread(s) per core:   2
    Core(s) per socket:   4
    Socket(s):            1
Besides other output above and below.
Strange that it has the same problem with showing the number CPUs, maybe it
needs a bug report too, so they also fix it.
The "CPU(s):" should match the "Socket(s):" as for sure my laptop has only one
socket and only one CPU (installed into that socket).

I think the confusion has at least these 2 causes:
1. The section comes after the "Software" section and it's called "Hardware".
So naturally I expected to see the hardware there, as it is, how matter how
other hardware (motherboard), the software (such as the firmware: UEFI / BIOS
or the kernel Linux:) sees is or changes it for the usage.
2. The way how it's displayed, with a number and a multiply sign in front of
the CPU's name (brand + model).
To me anyting that is shown as n x somehting, it means something times n (I
have something n times).
That item exists as many times as the nuber in front of it tells.
To add more to the confusion, if the user goes into the firmware or in the
kernel / systemd and enables / disable / changes configurations related to SMP
or HyperThreading, that number will change as the cores / threads allowed to be
used has been changed.
Which is clearly wrong as the CPU, its hardware, it's still the same, nothing
has been changed physically, only things how that physical piece of hardware is
used.
If the GPUs would also shown their VRAM and we played with ReBAR, the same
thing, the GPUs and their VRAM should still be displayed the same.
If only day storage is shown and we leave it unformatted or format it just half
of it, the same thing, the hardware it's still the same and should not be shown
how or how much of it it is used.
Physical characteristics should be shown.

Want to make a compromise and show a bit also changing parts of the hardware?
Then I thik something like what it has been done for the memory display could
be done, where the changing part (the usable memory) is shown now in
parentheses:
https://bugs.kde.org/show_bug.cgi?id=500412
There, other physical characteristics of the hardware were ommited (the meory
type, speed, slots) to show just that changing part in parentheses.
It might not be perfect or ideal for everybody, but I think it's probably a
good compromise to have a bit of the changing parts in the parentheses,
considering that a dedicated parge for Memory exits too.


(In reply to Oliver Beard from comment #4)
> I am inclined to think we probably want to show each physical CPU with a
> core and thread count:
> e.g. "12 × AMD Ryzen 5 5600X 6-Core Processor" -> AMD Ryzen 5 5600X (6
> cores, 12 threads)
That would be very nice and easy to understand!
But I would also make the code to display it also as:
2 x AMD Ryzen 5 5600X (6 cores, 12 threads)
For people who use dual-socket motherboards and have both of the sockets
populated with the same CPU.
I don't know if it's possible to have different type of CPUs on dual-socket
motherboards, like you can have with memory sticks on any motherboard.
Or it's it's possible, then display each on a new line, like when there are
multiple GPUs.
Unlike the case with multiple GPU, which I think a maximum of 5 are possible to
be installed, only 2 CPUs are possible to be installed.
This type of display I think it also leaves the CPU name (brand + model)
unchanged, no matter what the user changes in the firmware / Linux / systemd
configurations.

I think there should be a clear distinction between how the physical hardware
is, which should be displayed as close to possible as how it is on the shelf or
in its characterstics and how much of it is visible / usable, which can depend
on what kind of motherboard it has been installed into (x86 / ARM / RISC-V),
what other hardware devices are installed too (second CPUs RAM sticks, GPUs),
the firmware it uses (proprietarycoreboot / libreboot), the OS being used
(Linux, BSD, etc).
The changing parts (because that piece of hardwre is used in combination with
other hardware or software or configurations) should be displayed in the
parentheses, if that compromise is chosen.

Or leave it for the details page as they exist for the CPU and Memory.
Or leave it for the resource monitors (KDE's system monitor, Mission Center) as
it's more their job to show how the hardware is used.
But I would go with the compromise, showing the changing part in parentheses.
Since it's a hardware section, for the CPU I would like to see teh maximum
number of cores and threads possible).
Not the current maximum ones because I limited them from somewhere the firmware
of from Linux.
I think only the resource monitors should display the current ones.
Or if you want to display here on the summary page too, then they should be in
addition to the default (maximum ones), like with the memory (usable...)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to