All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Remove hpet vclock support
Date: Sat, 01 Feb 2014 16:43:34 +0100	[thread overview]
Message-ID: <52ED1626.7060905@ladisch.de> (raw)
In-Reply-To: <d348afdb2f6acc41dde0381396226b69a0358f8b.1391210357.git.luto@amacapital.net>

Andy Lutomirski wrote:
> The HPET is so amazingly slow that this is barely a win.

What happens on CPUs where the TSC cannot be used for the clock?

> it scares me a tiny bit to map a piece of crappy hardware where every
> userspace program can poke at it (even if said poking is read-only).
> Let's just remove it.

So this mapping is a backdoor to bypass the restrictions on /dev/hpet?  ;-)


Regards,
Clemens

  reply	other threads:[~2014-02-01 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 23:19 [PATCH] x86: Remove hpet vclock support Andy Lutomirski
2014-02-01 15:43 ` Clemens Ladisch [this message]
2014-02-01 17:10   ` Andy Lutomirski
2014-02-04 19:31 ` Thomas Gleixner
2014-02-04 19:41   ` Andy Lutomirski
2014-02-04 20:29     ` Thomas Gleixner

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=52ED1626.7060905@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --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 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.