mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] x86: APIC: Remove apic_write_around(); use alternatives
Date: Fri, 18 Jul 2008 12:52:59 +0200	[thread overview]
Message-ID: <20080718105259.GY6875@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.55.0807161837080.30858@cliff.in.clinika.pl>


* Maciej W. Rozycki <macro@linux-mips.org> wrote:

>  Use alternatives to select the workaround for the 11AP Pentium 
> erratum for the affected steppings on the fly rather than build time.  
> Remove the X86_GOOD_APIC configuration option and replace all the 
> calls to apic_write_around() with plain apic_write(), protecting 
> accesses to the ESR as appropriate due to the 3AP Pentium erratum.  
> Remove apic_read_around() and all its invocations altogether as not 
> needed.  Remove apic_write_atomic() and all its implementing backends.  
> The use of ASM_OUTPUT2() is not strictly needed for input constraints, 
> but I have used it for readability's sake.

wow, impressive patch!

>  I had the feeling no one else was brave enough to do it, so I went 
> ahead and here it is.  Verified by checking the generated assembly and 
> tested with both a 32-bit and a 64-bit configuration, also with the 
> 11AP "feature" forced on and verified with gdb on /proc/kcore to work 
> as expected (as an 11AP machines are quite hard to get hands on these 
> days).  Some script complained about the use of "volatile", but 
> apic_write() needs it for the same reason and is effectively a 
> replacement for writel(), so I have disregarded it.

kudos for pulling this off :-)

applied to tip/x86/apic. This will interact with tip/x86/x2apic but that 
topic is being worked on anyway. The interaction should be trivial.

	Ingo

  reply	other threads:[~2008-07-18 10:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 18:15 Maciej W. Rozycki
2008-07-18 10:52 ` Ingo Molnar [this message]
2008-07-18 16:25   ` Yinghai Lu
2008-07-18 17:01     ` Yinghai Lu
2008-07-18 21:03       ` Ingo Molnar
2008-07-18 21:13         ` Yinghai Lu
2008-07-18 22:02           ` Maciej W. Rozycki
2008-07-18 22:42             ` Zachary Amsden
2008-07-18 22:49               ` Suresh Siddha
2008-07-18 22:51                 ` Yinghai Lu
2008-07-18 23:00                   ` Suresh Siddha
2008-07-18 23:04                     ` Yinghai Lu
2008-07-18 23:18                       ` Suresh Siddha
2008-07-19 21:49                         ` Ingo Molnar
2008-07-19 21:53                           ` Ingo Molnar
2008-07-20 12:08                             ` Ingo Molnar
2008-07-20 15:04                               ` Ingo Molnar
2008-07-21 17:59                               ` Suresh Siddha
2008-07-22 13:24                                 ` Yong Wang
2008-07-22 13:48                                   ` Ingo Molnar
2008-07-18 23:43                 ` Zachary Amsden
2008-07-19 21:43                   ` Ingo Molnar
2008-07-18 22:58         ` Suresh Siddha
2008-07-19 21:47           ` Ingo Molnar

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=20080718105259.GY6875@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /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

Powered by JetHome