From: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "paul.burton@mips.com" <paul.burton@mips.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"jonas.gorski@gmail.com" <jonas.gorski@gmail.com>
Subject: Re: [PATCH] MIPS: Add CPU option reporting to /proc/cpuinfo
Date: Mon, 24 Dec 2018 14:43:29 +0000 [thread overview]
Message-ID: <4088FEE6-B2A4-49CE-8816-1A33D5443E21@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <89c9e62d-850c-2c78-3d09-269ce0c619a1@hauke-m.de>
> On 24 Dec 2018, at 13:42, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>
<snip>
> Hi Kevin,
>
> Normally you should not deactivate any features in cpu-feature-overrides.h which are supported by the CPU, when you do not define any thing the kernel will use auto detection.
>
> I think we should use the cpu_has_foo features as these are the features which could be used by user space applications, if it is only accidentally deactivated by the kernel, which should not happen, it could be that this feature is not fully set up by the kernel and will not work.
>
> Hauke
Fair enough.
Kevin
next prev parent reply other threads:[~2018-12-24 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 22:52 [PATCH] MIPS: Add CPU option reporting to /proc/cpuinfo Hauke Mehrtens
2018-12-24 9:03 ` Kevin 'ldir' Darbyshire-Bryant
2018-12-24 13:42 ` Hauke Mehrtens
2018-12-24 14:43 ` Kevin 'ldir' Darbyshire-Bryant [this message]
2018-12-25 21:35 ` Kevin 'ldir' Darbyshire-Bryant
2018-12-27 12:39 ` Hauke Mehrtens
2018-12-27 13:08 ` Kevin 'ldir' Darbyshire-Bryant
2019-01-03 21:49 ` Hauke Mehrtens
2019-01-03 23:13 ` Kevin 'ldir' Darbyshire-Bryant
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=4088FEE6-B2A4-49CE-8816-1A33D5443E21@darbyshire-bryant.me.uk \
--to=ldir@darbyshire-bryant.me.uk \
--cc=hauke@hauke-m.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
/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;
as well as URLs for NNTP newsgroup(s).