public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@cpushare.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: disable tsc with seccomp
Date: Mon, 21 Nov 2005 18:38:55 +0100	[thread overview]
Message-ID: <20051121173855.GI14746@opteron.random> (raw)
In-Reply-To: <20051121172444.GB20775@brahms.suse.de>

On Mon, Nov 21, 2005 at 06:24:44PM +0100, Andi Kleen wrote:
> I don't believe theoretical, unlikely to be usable in any way

Demonstrate it if you can.

The fact is that the closest thing to a demonstration that we have,
demonstrated the opposite of what you claim, so you'll have an hard
time to convince me about your point given you've no way to demonstrate
it.

I can guarantee that my machine is safe by running top, the only thing
that escapes the easy "top" check is CPUShare and I want to fix it,
since I can. 

> And in addition your change doesn't even close that channel
> in theory.

The the PCE is red herring, since it's a zero-cost addition.

  reply	other threads:[~2005-11-21 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 13:47 disable tsc with seccomp Andrea Arcangeli
2005-11-05 15:37 ` Andi Kleen
2005-11-05 16:07   ` Andrea Arcangeli
2005-11-05 16:12     ` Andi Kleen
2005-11-05 16:31       ` Andrea Arcangeli
2005-11-05 17:04         ` Andi Kleen
2005-11-06  1:55           ` Andrea Arcangeli
2005-11-21 16:43             ` Andrea Arcangeli
2005-11-21 17:05               ` Andi Kleen
2005-11-21 17:16                 ` Andrea Arcangeli
2005-11-21 17:24                   ` Andi Kleen
2005-11-21 17:38                     ` Andrea Arcangeli [this message]
2005-11-21 18:40                       ` Andrea Arcangeli

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=20051121173855.GI14746@opteron.random \
    --to=andrea@cpushare.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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