From: Pavel Machek <pavel@ucw.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, Piotr.Luc@intel.com,
dave.hansen@linux.intel.com
Subject: Re: [PATCH v11 0/5] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing
Date: Mon, 9 Jan 2017 10:12:38 +0100 [thread overview]
Message-ID: <20170109091238.GA19679@amd> (raw)
In-Reply-To: <alpine.DEB.2.20.1701090958350.3433@nanos>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Mon 2017-01-09 09:59:42, Thomas Gleixner wrote:
> On Tue, 3 Jan 2017, Pavel Machek wrote:
>
> > On Tue 2016-12-20 14:48:41, Grzegorz Andrejczuk wrote:
> > > Following patches enable the use of the feature that allows
> > > the Intel Xeon Phi x200 devices to use MONITOR/MWAIT instructions
> > > outside ring 0. It allows userspace applications to use
> > > more efficient synchronization operations, which improves performance
> > > and energy efficiency.
> >
> > What kind of security holes does it bring us?
> >
> > rdseed can be used for two processes to communicate when they should
> > not (serious problem for android). Can this be used for something similar?
>
> No. The monitor address must be in the virtual address space of the
> caller, so it's like any other 'read' operation.
Hmm. Unlike any other 'read' operation, it allows userland to modulate
CPU frequency with great precision; probably allowing userland to
transmit at radio bands, and allowing sound production without
syscalls (singing capacitors).
But userland can probably do that already, with help of
high-resolution timers, so nothing new theree... that I can think off.
Lets wait for the presentation at 39c3 :-).
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:[~2017-01-09 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 13:48 [PATCH v11 0/5] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing Grzegorz Andrejczuk
2016-12-20 13:48 ` [PATCH v11 1/5] x86/msr: add MSR_MISC_FEATURE_ENABLES and RING3MWAIT bit Grzegorz Andrejczuk
2016-12-21 20:23 ` Thomas Gleixner
2016-12-22 9:10 ` Andrejczuk, Grzegorz
2016-12-20 13:48 ` [PATCH v11 2/5] x86/elf: add HWCAP2 to expose ring 3 MONITOR/MWAIT Grzegorz Andrejczuk
2016-12-20 13:48 ` [PATCH v11 3/5] x86/cpufeature: add RING3MWAIT to CPU features Grzegorz Andrejczuk
2016-12-20 13:48 ` [PATCH v11 4/5] x86/cpufeature: enable RING3MWAIT for Knights Landing Grzegorz Andrejczuk
2016-12-20 18:31 ` [Patch " Grzegorz Andrejczuk
2016-12-21 20:24 ` Thomas Gleixner
2016-12-22 10:19 ` Andrejczuk, Grzegorz
2016-12-22 11:05 ` Thomas Gleixner
2016-12-22 11:37 ` Andrejczuk, Grzegorz
2016-12-22 14:20 ` Thomas Gleixner
2016-12-23 18:19 ` Andrejczuk, Grzegorz
2016-12-20 13:48 ` [PATCH v11 5/5] x86/cpufeature: enable RING3MWAIT for Knights Mill Grzegorz Andrejczuk
2017-01-03 22:09 ` [PATCH v11 0/5] Enabling Ring 3 MONITOR/MWAIT feature for Knights Landing Pavel Machek
2017-01-09 8:59 ` Thomas Gleixner
2017-01-09 9:12 ` 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=20170109091238.GA19679@amd \
--to=pavel@ucw.cz \
--cc=Piotr.Luc@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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