All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Athlon Prefetch workaround for 2.6.0test6
Date: Tue, 30 Sep 2003 14:27:29 +0100	[thread overview]
Message-ID: <20030930132729.GB23333@redhat.com> (raw)
In-Reply-To: <bla6lf$3ul$1@gatekeeper.tmr.com>

On Mon, Sep 29, 2003 at 09:02:39PM +0000, bill davidsen wrote:
 > In article <20030929125629.GA1746@averell>, Andi Kleen  <ak@muc.de> wrote:
 > 
 > | It removes the previous dumb in kernel workaround for this and shrinks the 
 > | kernel by >10k.
 > | 
 > | Small behaviour change is that a SIGBUS fault for a *_user access will
 > | cause an EFAULT now, no SIGBUS.
 > | 
 > | This version addresses all criticism that I got for previous versions.
 > | 
 > | - Only checks on AMD K7+ CPUs. 
 > | - Computes linear address for VM86 mode or code segments
 > | with non zero base.
 > | - Some cleanup
 > | - No pointer comparisons
 > | - More comments
 > 
 > I have to try this on a P4 and K7, but WRT "Only checks on AMD K7+ CPUs"
 > I hope you meant "only generates code if AMD CPU is target" and not that
 > the code size penalty is still there for CPUs which don't need it.

NO NO NO NO NO.
This *has* to be there on a P4 kernel too, as we can now boot those on a K7 too.
The 'code size penalty' you talk about is in the region of a few hundred
bytes. Much less than a page. There are far more obvious bloat candidates.

		Dave

-- 
 Dave Jones     http://www.codemonkey.org.uk

  parent reply	other threads:[~2003-09-30 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 12:56 [PATCH] Athlon Prefetch workaround for 2.6.0test6 Andi Kleen
2003-09-29 17:03 ` Jamie Lokier
2003-09-29 17:49   ` Andi Kleen
2003-09-29 20:08     ` Jamie Lokier
2003-09-30  5:50       ` Andi Kleen
2003-09-30  9:35       ` Gabriel Paubert
2003-09-29 22:13     ` Jamie Lokier
2003-09-30  5:38       ` Andi Kleen
2003-09-30  0:19     ` Jamie Lokier
2003-09-29 21:02 ` bill davidsen
2003-09-30  0:50   ` Nick Piggin
2003-09-30 13:27   ` Dave Jones [this message]
2003-09-30 15:36     ` Bill Davidsen
     [not found] <20030929125629.GA1746@averell.suse.lists.linux.kernel>
     [not found] ` <20030929170323.GC21798@mail.jlokier.co.uk.suse.lists.linux.kernel>
     [not found]   ` <20030929174910.GA90905@colin2.muc.de.suse.lists.linux.kernel>
     [not found]     ` <20030929200820.GA23444@mail.jlokier.co.uk.suse.lists.linux.kernel>
     [not found]       ` <20030930093556.GB12970@iram.es.suse.lists.linux.kernel>
2003-09-30  9:50         ` Andi Kleen

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=20030930132729.GB23333@redhat.com \
    --to=davej@redhat.com \
    --cc=davidsen@tmr.com \
    --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 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.