public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Neil Brown <nfbrown@novell.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH RFC] x86: hpet: Avoid the readback penalty
Date: Thu, 16 Sep 2010 21:04:50 +0100	[thread overview]
Message-ID: <87d3sdfo9p.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <alpine.LFD.2.00.1009151500060.2416@localhost6.localdomain6> (Thomas Gleixner's message of "Wed, 15 Sep 2010 15:11:57 +0200 (CEST)")

On 15 Sep 2010, Thomas Gleixner said:

> On Tue, 14 Sep 2010, tip-bot for Thomas Gleixner wrote:
>> x86: hpet: Work around hardware stupidity
>
> After my brain recovered from yesterdays exposure with the x86 timer
> horror, I came up with a different solution for this problem, which
> avoids the readback of the compare register completely. It works
> nicely on my affected ATI system, but needs some exposure to the other
> machines.
>
> Comments ?

Works for me. (I still have boot problems, but these seem to be
NFS-related: -ESTALE from an apparently random subset of my mount points
at initial mount time. Restarting rpc.mountd on the server fixes
it. This is with nfs-utils 1.2.2, but I see it right up to 60abb98, that
being the most recent version I tested. This doesn't happen if the
client is running 2.6.34.x, as far as I can tell. It also doesn't happen
with all my 2.6.35.x clients. Sigh. I hate bugs like this.)

  parent reply	other threads:[~2010-09-16 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-54ff7e595d763d894104d421b103a89f7becf47c@git.kernel.org>
2010-09-14 23:36 ` [tip:x86/urgent] x86: hpet: Work around hardware stupidity Venkatesh Pallipadi
2010-09-15 13:11 ` [PATCH RFC] x86: hpet: Avoid the readback penalty Thomas Gleixner
2010-09-15 13:43   ` Anders Larsen
2010-09-15 13:54   ` John Drescher
     [not found]     ` <AANLkTikHfDUh3LdmyA5eMNACFPfi6pqGLFJiyzVm79X_@mail.gmail.com>
2010-09-16  4:45       ` Fwd: " John Drescher
2010-09-15 14:40   ` Borislav Petkov
2010-09-15 14:42     ` Thomas Gleixner
2010-09-16 12:28     ` Borislav Petkov
2010-09-16 20:04   ` Nix [this message]
2010-09-18  7:49   ` Damien Wyart
2010-09-18  9:41     ` Thomas Gleixner
2010-09-18 13:43     ` Nix
2010-09-18 10:13   ` [tip:x86/timers] x86: Hpet: Avoid the comparator " tip-bot for 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=87d3sdfo9p.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfbrown@novell.com \
    --cc=tglx@linutronix.de \
    /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