[Top] [All Lists]

Re: [PATCH] mm/pg-r4k.c: Dump the generated code

To: Geert Uytterhoeven <>
Subject: Re: [PATCH] mm/pg-r4k.c: Dump the generated code
From: Franck Bui-Huu <>
Date: Mon, 08 Oct 2007 17:02:11 +0200
Cc: "Maciej W. Rozycki" <>, Ralf Baechle <>, Thiemo Seufer <>,
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=lOR8VbnmHH7Rh8hzyz6WybuvTHCMIbp4lFPnpwX/k7M=; b=RtnVHc3v+1tBMCt3NWmiOHYaRbxDNZB5Ur1oOysNhrnc/pCNERfdWp5I7yM8rXYw5hkc0w1SqQXkJSxKrI3U6EoqomYCmk9lLNIwyak+y+lXhfjUR7KP9ULi/sMOy91V64FK2g7tlRp6kKZroBVckXwyEq/n7nr8HYO5vvPBTJY=
Domainkey-signature: a=rsa-sha1; c=nofws;; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=JSFwQI8oXzfxdNQZidFu7MxmmAMcO3lrm8dY2bFNpskbJ0qKkEOTi/y/HMg/FscHGWbDoVI0wLcmbSZP2ZdKJnz1l25fUvw5GEI5kepx+aVjErZDSSr1J6JVLKIQRdcffTnDXKpmM+l4m1kJ/7xhdesK9RAQlXfhYgL4eQDFgmk=
In-reply-to: <Pine.LNX.4.64.0710051102300.32066@anakin>
Original-recipient: rfc822;
References: <> <> <> <> <> <> <> <> <> <> <> <> <Pine.LNX.4.64.0710051102300.32066@anakin>
User-agent: Thunderbird (X11/20070719)
Geert Uytterhoeven wrote:
> For specialized systems, you can always introduce the option to generate
> the TLB handler at compile time:

What do you mean by "specialized system" ?

If for some platforms we could generate the TLB handlers at compile
time, we could do it for all platforms, specially if the handler only
depends on the cpu type, no ?

>   - Enhance tlbex.c to be able to compile it for the host, and generate
>     a fixed TLB handler, based on CONFIG_* options, if
>     CONFIG_STATIC_TLB_HANDLER (buried deep in depends on EMBEDDED &&

It may mean putting a lot of hacks in tlbex.c making it just a PITA to
enhance and to maintain. IMHO, just have a static TLB handler
generator is simpler specially if we don't need to patch the handler
later. But we need to be sure nothing can be discover at runtime only
for current and future supported cpus...


<Prev in Thread] Current Thread [Next in Thread>