On Sun, 2020-08-30 at 13:50 +0200, Borislav Petkov wrote:
> On Fri, Aug 28, 2020 at 03:30:32PM -0700, Kyung Min Park wrote:
> > Should I mention the tool specifically although the tool is WIP?
>
> Well, if you wanna look at it that way, the whole kernel is
> constantly
> and forever WIP. :-)
>
>
On Fri, Aug 28, 2020 at 03:30:32PM -0700, Kyung Min Park wrote:
> Should I mention the tool specifically although the tool is WIP?
Well, if you wanna look at it that way, the whole kernel is constantly
and forever WIP. :-)
Also, if there's some functionality missing, pointing to it might make
Hi Boris,
On Fri, 2020-08-28 at 20:42 +0200, Borislav Petkov wrote:
> On Mon, Aug 24, 2020 at 11:04:12AM -0700, Kyung Min Park wrote:
> > +If the expected flag does not appear in /proc/cpuinfo, things are
> > murkier.
> > +Users need to find out the reason why the flag is missing and find
> > the
On Mon, Aug 24, 2020 at 11:04:12AM -0700, Kyung Min Park wrote:
> +If the expected flag does not appear in /proc/cpuinfo, things are murkier.
> +Users need to find out the reason why the flag is missing and find the way
> +how to enable it, which is not always easy. There are several factors that
/proc/cpuinfo shows features which the kernel supports. Some of these
flags are derived from CPUID, and others are derived from other sources,
including some that are entirely software-based. Currently, there is
not any documentation in the kernel about how /proc/cpuinfo flags are
generated and
5 matches
Mail list logo
