From: Pavel Machek <pavel@ucw.cz>
To: Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, bp@suse.de, dave.hansen@linux.intel.com,
lukasz.daniluk@intel.com, james.h.cownie@intel.com,
jacob.jun.pan@intel.com, Piotr.Luc@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/4] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing
Date: Sat, 3 Dec 2016 21:27:51 +0100 [thread overview]
Message-ID: <20161203202751.GC13417@amd> (raw)
In-Reply-To: <1477662595-21011-1-git-send-email-grzegorz.andrejczuk@intel.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Fri 2016-10-28 15:49:51, Grzegorz Andrejczuk wrote:
> These patches enable Intel Xeon Phi x200 feature to use MONITOR/MWAIT
> instruction in ring 3 (userspace) Patches set MSR 0x140 for all
logical CPUs.
> Then expose it as CPU feature and introduces elf HWCAP capability
> for x86.
Elf hardware capability? Why do that? Normally CPU features go to
/proc/cpuinfo...
Plus... Can you elaborate on security effects of this? Does monitor
allow monitoring memory the current process can not write to? Is it
good idea to let userland process watch for NMIs?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-12-03 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 13:49 [PATCH v7 0/4] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing Grzegorz Andrejczuk
2016-10-28 13:49 ` [PATCH v7 1/4] x86/msr: Add MSR(140H) and PHIR3MWAIT bit to msr-info.h Grzegorz Andrejczuk
2016-10-31 1:14 ` Thomas Gleixner
2016-10-28 13:49 ` [PATCH v7 2/4] x86: Use HWCAP2 to expose Xeon Phi ring 3 MWAIT Grzegorz Andrejczuk
2016-10-31 1:14 ` Thomas Gleixner
2016-10-28 13:49 ` [PATCH v7 3/4] x86/cpufeature: Add PHIR3MWAIT to CPU features Grzegorz Andrejczuk
2016-10-31 1:15 ` Thomas Gleixner
2016-10-28 13:49 ` [PATCH v7 4/4] x86: Add enabling of the R3MWAIT during boot Grzegorz Andrejczuk
2016-10-31 1:15 ` Thomas Gleixner
2016-12-03 20:27 ` Pavel Machek [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=20161203202751.GC13417@amd \
--to=pavel@ucw.cz \
--cc=Piotr.Luc@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=james.h.cownie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.daniluk@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).