All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: "Madajczak, Tomasz" <Tomasz.Madajczak@intel.com>
Cc: Ben Widawsky <ben@bwidawsk.net>,
	"Intel-gfx@lists.freedesktop.org"
	<Intel-gfx@lists.freedesktop.org>
Subject: Re: pin OABUFFER to GGTT
Date: Wed, 2 Jul 2014 11:49:16 +0100	[thread overview]
Message-ID: <20140702104916.GB26852@strange.amr.corp.intel.com> (raw)
In-Reply-To: <F4B171067D52CE4D8BE01C491BC4F26634E26C65@IRSMSX106.ger.corp.intel.com>

On Wed, Jul 02, 2014 at 10:31:45AM +0000, Madajczak, Tomasz wrote:
> There isn't any secret or privacy in that OA buffer data - just
> results of performance counters, shown by tools such as GPA/ Vtune.

Chris alludes to the fact that if there's a way for one application to
gather data about other applications (whatever kind of data), that's an
automatic security concern.

One may think that's only very theoretical, but the side channel attacks
are (surpringly) real and effective. It cannot be proven easily that
exposing data about other contexes is totally secure.

There are ways around that however. If only root can gather that data, I
think we've contained the issue enough for the case at hand?

-- 
Damien

  reply	other threads:[~2014-07-02 10:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 16:24 pin OABUFFER to GGTT Mateo Lozano, Oscar
2014-07-01 16:30 ` Chris Wilson
2014-07-01 16:34   ` Mateo Lozano, Oscar
2014-07-01 16:51     ` Chris Wilson
2014-07-01 17:13       ` Mateo Lozano, Oscar
2014-07-01 17:16       ` Mateo Lozano, Oscar
2014-07-01 19:54         ` Chris Wilson
2014-07-02  6:40           ` Ben Widawsky
2014-07-02  6:55             ` Chris Wilson
2014-07-02  8:49               ` Mateo Lozano, Oscar
2014-07-02 10:31                 ` Madajczak, Tomasz
2014-07-02 10:49                   ` Damien Lespiau [this message]
2014-07-02 11:11                     ` Madajczak, Tomasz
2014-07-02 13:19                       ` Rutkowski, Adam J
2014-07-03  7:17                         ` Damien Lespiau
2014-07-03 17:10                           ` Ben Widawsky
2014-07-03 20:45                             ` Ben Widawsky
2014-07-02 17:36                   ` Ben Widawsky
2014-07-07 20:43           ` Daniel Vetter
2014-07-07 23:59             ` Bragg, Robert

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=20140702104916.GB26852@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=Tomasz.Madajczak@intel.com \
    --cc=ben@bwidawsk.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.