(no subject)

From: John Bradford (john_at_grabjohn.com)
Date: 09/30/03

  • Next message: Helge Hafting: "Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant." 
    Date:	Tue, 30 Sep 2003 09:17:16 +0100
To: Jamie Lokier <jamie@shareable.org>, akpm@osdl.org

    richard.brunner@amd.com
    In-Reply-To: <20030930073814.GA26649@mail.jlokier.co.uk>
    References: <20030930073814.GA26649@mail.jlokier.co.uk>
    Subject: Re: [PATCH] Mutilated form of Andi Kleen's AMD prefetch errata patch

    Quote from Jamie Lokier <jamie@shareable.org>:

    > 2. Nevertheless, when a kernel _not_ optimised for those AMD processors
    > is run on one, the "alternative" mechanism now correctly replaces
    > prefetch instructions with nops.

    > It's a reasonable argument that if a kernel version, say 2.6.0, promises
    > to hide the errata from _userspace_ programs, then the generic or
    > not-AMD-optimised kernels should do that too. Otherwise userspace may
    > as well provide the workaround itself, by catching SIGSEGV - because it
    > is perfectly normal and common to run a generic kernel on an AMD.

    This problem, and others like it, would be solved for ever with
    Adrian's bitmap-of-supported-cpus patch, though. With that, there is
    no 'generic' kernel, either it supports Athlons, or it doesn't. 100%
    elimination of Athlon specific code for other CPUs. Everybody is
    happy.

    Of course a kernel compiled strictly for 386s may seem to boot on an
    Athlon but not work properly. So what? Just don't run the 'wrong'
    kernel.

    John.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Helge Hafting: "Re: -mregparm=3 (was Re: [PATCH] i386 do_machine_check() is redundant."

    Relevant Pages

    • Re: RT patch acceptance
      ... judge the complexity of a design for that type of system. ... claim that you cannot judge the complexity of a kernel modification. ... Since the patch in question doesn't actually need that information to ... nanokernel's API up to date with additions to Linux's API that RT people ...
      (Linux-Kernel)
    • Re: inline asm semantics: output constraint width smaller than input
      ... Now in this case the patch you suggest might end up hurting the end result ... The below patch is to build the kernel for x86_64, ... # Device Drivers ... # PCI IDE chipsets support ...
      (Linux-Kernel)
    • [RFC] Making percpu module variables have their own memory.
      ... Someone using the -rt patch found that one of the tracing options caused ... 64K for every CPU to cover all the per_cpu variables used in the kernel ... static void wakeup_softirqd_prio ...
      (Linux-Kernel)
    • Re: This is [Re:] How to improve the quality of the kernel[?].
      ... The -mm kernel already implements what your proposed PTS would do. ... If patch have no TS ID, ... Thus i can apply for example lguest patches and implement and test new ... How many open source projects use Bugzilla and how many use the Debian BTS? ...
      (Linux-Kernel)
    • Re: Documentation - how to apply patches for various trees
      ... >> explanation of the various kernel trees and how to apply their patches. ... +a patch to the kernel or, more specifically, what base kernel a patch for ... +and what new version the patch will change the source tree into. ...
      (Linux-Kernel)