From: Wei Yang <richard.weiyang@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 1/5] memblock test: fix implicit declaration of function 'virt_to_phys'
Date: Mon, 5 Aug 2024 15:37:20 +0000 [thread overview]
Message-ID: <20240805153720.myjqd6ur65x5ucsu@master> (raw)
In-Reply-To: <ZrCjYqdmNfn3di-o@kernel.org>
On Mon, Aug 05, 2024 at 01:03:14PM +0300, Mike Rapoport wrote:
>On Fri, Aug 02, 2024 at 01:09:19AM +0000, Wei Yang wrote:
>> Commit 94ff46de4a73 ("memblock: Move late alloc warning down to phys
>> alloc") introduce the usage of virt_to_phys(), which is not defined in
>> memblock tests.
>>
>> Define it in mm.h to fix the build error.
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>>
>> ---
>> v3: use static inline as phys_to_virt
>> v2: move definition to mm.h
>> ---
>> tools/include/linux/mm.h | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/tools/include/linux/mm.h b/tools/include/linux/mm.h
>> index cad4f2927983..c9e915914add 100644
>> --- a/tools/include/linux/mm.h
>> +++ b/tools/include/linux/mm.h
>> @@ -25,6 +25,12 @@ static inline void *phys_to_virt(unsigned long address)
>> return __va(address);
>> }
>>
>> +#define virt_to_phys virt_to_phys
>> +static inline phys_addr_t virt_to_phys(volatile void *address)
>
>Why volatilte?
>
There are two definitions of virt_to_phys:
include/asm-generic/io.h
arch/x86/include/asm/io.h
both has volatile.
I just copy from it. But I don't 100% understand it.
>> +{
>> + return (unsigned long)address;
>
>This should be phys_addr_t, look at its definition in tools/include/linux/types.h
>
You are right. Will fix it.
>> +}
>> +
>> void reserve_bootmem_region(phys_addr_t start, phys_addr_t end, int nid);
>>
>> static inline void totalram_pages_inc(void)
>> --
>> 2.34.1
>>
>
>--
>Sincerely yours,
>Mike.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-08-05 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 1:09 Wei Yang
2024-08-02 1:09 ` [PATCH v3 2/5] memblock test: add the definition of __setup() Wei Yang
2024-08-02 1:09 ` [PATCH v3 3/5] memblock test: fix implicit declaration of function 'memparse' Wei Yang
2024-08-02 1:09 ` [PATCH v3 4/5] memblock test: fix implicit declaration of function 'isspace' Wei Yang
2024-08-02 1:09 ` [PATCH v3 5/5] memblock test: fix implicit declaration of function 'strscpy' Wei Yang
2024-08-05 10:03 ` [PATCH v3 1/5] memblock test: fix implicit declaration of function 'virt_to_phys' Mike Rapoport
2024-08-05 15:37 ` Wei Yang [this message]
2024-08-05 17:05 ` Mike Rapoport
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=20240805153720.myjqd6ur65x5ucsu@master \
--to=richard.weiyang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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