Re: [PATCH v6 01/11] moduleparam: add data member to struct kernel_param

From: jim.cromie@gmail.com
To: Jason Baron <jbaron@akamai.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Sean Paul <seanpaul@chromium.org>,  Jessica Yu <jeyu@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	 dri-devel <dri-devel@lists.freedesktop.org>,
	 amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
	intel-gvt-dev@lists.freedesktop.org,
	 Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v6 01/11] moduleparam: add data member to struct kernel_param
Date: Fri, 27 Aug 2021 12:04:39 -0600	[thread overview]
Message-ID: <CAJfuBxz83LUFqPmApV22d0R1pHxFH4ZhObi7PgQeQ75w4zvb7A@mail.gmail.com> (raw)
In-Reply-To: <c83b0814-b8e1-91f5-ba28-f9db3f363ce1@akamai.com>

On Wed, Aug 25, 2021 at 11:13 AM Jason Baron <jbaron@akamai.com> wrote:
>
>
>
> On 8/22/21 6:19 PM, Jim Cromie wrote:
> > Add a const void* data member to the struct, to allow attaching
> > private data that will be used soon by a setter method (via kp->data)
> > to perform more elaborate actions.
> >
> > To attach the data at compile time, add new macros:
> >

>
> I wonder if kp->arg can just be used for all this and avoid this patch entirely?
>
> define something like:
>
> struct dd_bitmap_param {
>         int bitmap;
>         struct dyndbg_bitdesc *bitmap_arr;
> };
>
> and then just pass a pointer to it as 'arg' for module_param_cb? And then in
> the get/set callbacks you can use kp->bitmap and kp->bitmap_arr.
>

yes, thanks, this is working out nicely.
I think I was thrown off by the arg name,
if it had been called data, it would have slapped me

> Thanks,
>
> -Jason
>