Linux Modules
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@meta.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Song Liu <song@kernel.org>,
	"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Kernel Team <kernel-team@meta.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH v5] module: replace module_layout with module_memory
Date: Wed, 1 Feb 2023 16:50:47 +0000	[thread overview]
Message-ID: <8F559BD9-D7D4-4669-9C87-0582F06E730F@fb.com> (raw)
In-Reply-To: <Y9o52aAC33YlRueI@hirez.programming.kicks-ass.net>



> On Feb 1, 2023, at 2:07 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> 
[...]

> 
> ... you write something like:
> 
> #define for_class_mod_mem_type(type, class) \
> for_each_mod_mem_type(type) \
> if (mod_mem_type_is_##class(type))
> 
> Then we can write things like:
> 
> for_class_mod_mem_type(type, init)
> for_class_mod_mem_type(type, data)
> 
> and
> 
> for_class_mod_mem_type(type, core_data)
> 
> (this last could be used in show_datasize() for example).
> 
> Does that make sense?

It sure does. Let me give it a try. 

Thanks,
Song

      reply	other threads:[~2023-02-01 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  6:47 [PATCH v5] module: replace module_layout with module_memory Song Liu
2023-02-01 10:07 ` Peter Zijlstra
2023-02-01 16:50   ` Song Liu [this message]

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=8F559BD9-D7D4-4669-9C87-0582F06E730F@fb.com \
    --to=songliubraving@meta.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=hch@lst.de \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mcgrof@kernel.org \
    --cc=peterz@infradead.org \
    --cc=song@kernel.org \
    --cc=tglx@linutronix.de \
    /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