From: "Felix Schnizlein" <fschnizlein@suse.com>
To: <gregkh@linuxfoundation.org>
Cc: <yanmin.zhang@intel.com>, <x86@kernel.org>, <mingo@redhat.com>,
"Thomas Renninger" <trenn@suse.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] Implement sysfs based cpuinfo for x86 cpus.
Date: Wed, 02 Aug 2017 23:47:16 +0200 [thread overview]
Message-ID: <59824864020000EE001C9890@smtp.nue.novell.com> (raw)
In-Reply-To: <20170802174725.GB2333@kroah.com>
>>> Greg KH <gregkh@linuxfoundation.org> 08/02/17 7:47 PM >>>
On Wed, Aug 02, 2017 at 07:35:16PM +0200, Felix Schnizlein wrote:
>> Enable sysfs cpuinfo for x86 based cpus. Export often used cpu
>> information to sysfs. Stepping, cpu flags, cpu bugs, bogomips,
>> cpu family, vendor_id, model, and model_name are exported.
>>
>> Sysfs documentation is updated to reflect changes.
>>
>> Signed-off-by: Felix Schnizlein <fschnizlein@suse.com>
>> Signed-off-by: Thomas Renninger <trenn@suse.com>
>> ---
>>
>> Changes since v1:
>> - add missing documentation parts
>> - fix wording in documentation description
> Note, your subject lines could use a bit better work. How about:
> cpuinfo: implement sysfs nodes for x86
True, I will update them accordingly when I repost the next time.
>
> That makes it easier to see/sort in my inbox. Same for patch 1.
>
> Anyway, I'd really like to see this for another cpu arch at the same
> time, just to verify you really have the correct api/interface here.
> Can you do it for arm64 or something else as well?
Sure, I will look into what devices are available for me and implement
another arch.
Felix
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2017-08-02 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1501695316-17265-1-git-send-email-fschnizlein@suse.com>
[not found] ` <1501695316-17265-3-git-send-email-fschnizlein@suse.com>
2017-08-02 17:47 ` Greg KH
2017-08-02 21:47 ` Felix Schnizlein [this message]
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=59824864020000EE001C9890@smtp.nue.novell.com \
--to=fschnizlein@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=trenn@suse.com \
--cc=x86@kernel.org \
--cc=yanmin.zhang@intel.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
all inboxes | Powered by JetHome®