linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mips: cm: Convert __mips_cm_l2sync_phys_base() to weak function
Date: Mon, 11 Mar 2024 14:07:19 +0100	[thread overview]
Message-ID: <Ze8CB27Ad427Gk3K@alpha.franken.de> (raw)
In-Reply-To: <6n2synlvazjh2gptxtioju7dciwshwqyei4xnfzorns66b3hqx@c7blt5kwnpbl>

On Mon, Feb 26, 2024 at 04:11:05PM +0300, Serge Semin wrote:
> On Mon, Feb 26, 2024 at 01:29:54PM +0100, Arnd Bergmann wrote:
> > On Mon, Feb 26, 2024, at 13:20, Serge Semin wrote:
> > > On Mon, Feb 26, 2024 at 01:04:33PM +0100, Arnd Bergmann wrote:
> > >> On Mon, Feb 26, 2024, at 12:27, Serge Semin wrote:
> > 
> > > I see your point now. Thanks for clarification. IMO it would be less
> > > readable due to the ifdef-ery and the new config, and less
> > > maintainable due to the conditional compilation, but would provide a
> > > more performant solution since the compiler will be able to inline the
> > > singly used static method. Basically you suggest to emulate the weak
> > > implementation by an additional kernel config.
> > 
> > I mean the kernel config that you already need here, since
> > the strong version of the function is already optional.
> 
> Why would I need it if after this patch is applied the
> mips_cm_l2sync_phys_base() method will be converted to a global weak
> implementation?
> 
> > 
> > > Not sure whether it would be better than a well-known
> > > weak-attribute-based pattern. Anyway let's wait for the
> > > Thomas' opinion about your suggestion. If he thinks
> > > it would be better I'll update the patches.
> > 
> > Weak functions are not used all that much outside of a
> > couple of parts of the kernel. There is a lot of them
> > in drivers/pci/, a little bit in acpi and efi, and
> > then a bit in arch/*/, though most of that is in mips.
> 
> + a lot of them in kernel/*, some in mm/* .)
> 
> > 
> > Ifdef checks in .c files are not great, but at least they
> > are much more common than __weak functions and self-documenting.
> 
> Ok. I don't have concretely strong opinion about what is better. Let's
> wait for what Thomas thinks about this.

I've taken your patches as we get rid of this alias thing. As long as
there is no big push against __weak I'm ok with this case.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2024-03-11 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 10:54 [PATCH v2 0/2] MIPS: Fix missing proto and passing arg warnings Serge Semin
2024-02-26 10:54 ` [PATCH v2 1/2] mips: cm: Convert __mips_cm_l2sync_phys_base() to weak function Serge Semin
2024-02-26 11:04   ` Arnd Bergmann
2024-02-26 11:27     ` Serge Semin
2024-02-26 12:04       ` Arnd Bergmann
2024-02-26 12:20         ` Serge Semin
2024-02-26 12:29           ` Arnd Bergmann
2024-02-26 13:11             ` Serge Semin
2024-03-11 13:07               ` Thomas Bogendoerfer [this message]
2024-02-26 10:54 ` [PATCH v2 2/2] mips: cm: Convert __mips_cm_phys_base() " Serge Semin
2024-03-11 13:05 ` [PATCH v2 0/2] MIPS: Fix missing proto and passing arg warnings Thomas Bogendoerfer

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=Ze8CB27Ad427Gk3K@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=Alexey.Malahov@baikalelectronics.ru \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=fancer.lancer@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).