From: Randy Dunlap <rdunlap@infradead.org>
To: Song Liu <song@kernel.org>, linux-kernel@vger.kernel.org
Cc: bpf@vger.kernel.org, mcgrof@kernel.org, peterz@infradead.org,
tglx@linutronix.de, x86@kernel.org, rppt@kernel.org,
kent.overstreet@linux.dev
Subject: Re: [PATCH 1/3] module: Introduce module_alloc_type
Date: Thu, 25 May 2023 23:07:30 -0700 [thread overview]
Message-ID: <b6c6eab1-9e81-4247-ee92-4684dae78c15@infradead.org> (raw)
In-Reply-To: <20230526051529.3387103-2-song@kernel.org>
Hi--
On 5/25/23 22:15, Song Liu wrote:
> +/**
> + * struct vmalloc_params - Parameters to call __vmalloc_node_range()
> + * @start: Address space range start
> + * @end: Address space range end
> + * @gfp_mask: The gfp_t mask used for this range
> + * @pgprot: The page protection for this range
> + * @vm_flags The vm_flag used for this range
* @vm_flags:
> + */
> +struct vmalloc_params {
> + unsigned long start;
> + unsigned long end;
> + gfp_t gfp_mask;
> + pgprot_t pgprot;
> + unsigned long vm_flags;
> +};
--
~Randy
next prev parent reply other threads:[~2023-05-26 6:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 5:15 [PATCH 0/3] Type aware module allocator Song Liu
2023-05-26 5:15 ` [PATCH 1/3] module: Introduce module_alloc_type Song Liu
2023-05-26 6:07 ` Randy Dunlap [this message]
2023-05-26 22:29 ` Kent Overstreet
2023-05-26 23:09 ` Song Liu
2023-05-26 23:39 ` Kent Overstreet
2023-05-27 0:03 ` Song Liu
2023-05-27 3:19 ` Kent Overstreet
2023-05-27 6:00 ` Song Liu
2023-05-26 5:15 ` [PATCH 2/3] ftrace: Add swap_func to ftrace_process_locs() Song Liu
2023-05-26 5:15 ` [PATCH 3/3] x86/module: Use module_alloc_type Song Liu
2023-05-27 7:04 ` [PATCH 0/3] Type aware module allocator Kent Overstreet
2023-05-28 5:58 ` Song Liu
2023-05-29 10:45 ` Mike Rapoport
2023-05-30 22:37 ` Song Liu
2023-05-31 13:51 ` Mike Rapoport
2023-05-31 17:03 ` Song Liu
2023-05-29 18:25 ` Kent Overstreet
2023-05-30 22:48 ` Song Liu
2023-06-01 17:53 ` Kent Overstreet
2023-06-01 18:21 ` Kent Overstreet
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=b6c6eab1-9e81-4247-ee92-4684dae78c15@infradead.org \
--to=rdunlap@infradead.org \
--cc=bpf@vger.kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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).