linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	<catalin.marinas@arm.com>, <will@kernel.org>,
	<akpm@linux-foundation.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: <linux-mm@kvack.org>, <hch@infradead.org>, <arnd@arndb.de>
Subject: Re: [PATCH v2 3/5] mm: ioremap: Add arch_ioremap/iounmap()
Date: Thu, 19 May 2022 14:24:27 +0800	[thread overview]
Message-ID: <06e86db8-0797-1610-48e3-c607cfacf8f7@huawei.com> (raw)
In-Reply-To: <871657f3-9c26-a56a-03d2-29b1915001c9@arm.com>


On 2022/5/19 12:46, Anshuman Khandual wrote:
> Hi Kefeng,
>
> On 4/29/22 16:02, Kefeng Wang wrote:
>> Add special hook for architecture to verify addr, size and prot
>> or setup when ioremap() or iounmap(), which will make the generic
>> ioremap more useful.
>>
>>    arch_ioremap() return a 'void __iomem *',
>>      - IS_ERR means return an error
>>      - NULL means continue to remap
>>      - a non-NULL, non-IS_ERR pointer is directly returned
>>    arch_iounmap() return a int value,
>>      - 0 means continue to vunmap
>>      - error code means skip vunmap and return directly
> Should not these comments be also included as in-code documentation, possibly
> near generic fall back stubs for arch_ioremap()/arch_iounmap() in the header
> include/asm-generic/io.h ?
Ok, I will add some document in io.h
>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   include/asm-generic/io.h | 14 ++++++++++++++
>>   mm/ioremap.c             | 14 +++++++++++++-
>>   2 files changed, 27 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/asm-generic/io.h b/include/asm-generic/io.h
>> index e6ffa2519f08..f2f9aeedb5e8 100644
>> --- a/include/asm-generic/io.h
>> +++ b/arch_iounmap
>> @@ -964,6 +964,20 @@ static inline void iounmap(volatile void __iomem *addr)
>>   #elif defined(CONFIG_GENERIC_IOREMAP)
>>   #include <linux/pgtable.h>
>>   
>> +#ifndef arch_ioremap
>> +static inline void __iomem *arch_ioremap(phys_addr_t phys_addr, size_t size, unsigned long prot)
>> +{
>> +	return NULL;
>> +}
>> +#endif
>> +
>> +#ifndef arch_iounmap
>> +static inline int arch_iounmap(void __iomem *addr)
>> +{
>> +	return 0;
>> +}
>> +#endif
> There is a function in arch/arm/ with exact same name although the platform does
> not enable GENERIC_IOREMAP. That function would require renaming for these arch
> callbacks to be added here in GENERIC_IOREMAP path. Otherwise, it might be just
> confusing later.
>
> git grep "arch_iounmap" arch/arm/
>
> arch/arm/include/asm/io.h:extern void (*arch_iounmap)(volatile void __iomem *);
> arch/arm/mm/ioremap.c:void (*arch_iounmap)(volatile void __iomem *) = __iounmap;
> arch/arm/mm/ioremap.c:  arch_iounmap(cookie);
> arch/arm/mm/nommu.c:void (*arch_iounmap)(volatile void __iomem *);

After

   59d3ae9a5bf60 ("ARM: remove Intel iop33x and iop13xx support") v5.4
   3e3f354bc383a ("ARM: remove ebsa110 platform") v5.11

arch_iounmap is useless, we could directly kill arch_iounmap/__iounmap 
on arm,

will add new cleanup patch in v3.


>
>> +
>>   void __iomem *ioremap_prot(phys_addr_t phys_addr, size_t size, unsigned long prot);
>>   void iounmap(volatile void __iomem *addr);
>>   
>> diff --git a/mm/ioremap.c b/mm/ioremap.c
>> index 7cb9996b0c12..de5a2e899e14 100644
>> --- a/mm/ioremap.c
>> +++ b/mm/ioremap.c
>> @@ -16,6 +16,7 @@ void __iomem *ioremap_prot(phys_addr_t phys_addr, size_t size, unsigned long pro
>>   	unsigned long offset, vaddr;
>>   	phys_addr_t last_addr;
>>   	struct vm_struct *area;
>> +	void __iomem *base;
>>   
>>   	/* Disallow wrap-around or zero size */
>>   	last_addr = phys_addr + size - 1;
>> @@ -27,6 +28,12 @@ void __iomem *ioremap_prot(phys_addr_t phys_addr, size_t size, unsigned long pro
>>   	phys_addr -= offset;
>>   	size = PAGE_ALIGN(size + offset);
>>   
>> +	base = arch_ioremap(phys_addr, size, prot);
>> +	if (IS_ERR(base))
>> +		return NULL;
>> +	else if (base)
>> +		return base;
>> +
>>   	area = get_vm_area_caller(size, VM_IOREMAP,
>>   			__builtin_return_address(0));
>>   	if (!area)
>> @@ -45,6 +52,11 @@ EXPORT_SYMBOL(ioremap_prot);
>>   
>>   void iounmap(volatile void __iomem *addr)
>>   {
>> -	vunmap((void *)((unsigned long)addr & PAGE_MASK));
>> +	void *vaddr = (void *)((unsigned long)addr & PAGE_MASK);
> Should not this variable be 'void __iomem *vaddr' instead, like above in
> ioremap_prot(). Because arch_iounmap() takes 'void __iomem *' instead.

Will do, thanks.

>> +
>> +	if (arch_iounmap(vaddr))
>> +		return;
>> +
>> +	vunmap(vaddr);
>>   }
>>   EXPORT_SYMBOL(iounmap);
> - Anshuman
> .


  reply	other threads:[~2022-05-19  6:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 10:32 [PATCH v2 0/5] arm64: Cleanup ioremap() and support ioremap_prot() Kefeng Wang
2022-04-29 10:32 ` [PATCH v2 1/5] mm: ioremap: Use more sensibly name in ioremap_prot() Kefeng Wang
2022-05-02  9:38   ` Anshuman Khandual
2022-04-29 10:32 ` [PATCH v2 2/5] mm: ioremap: Setup phys_addr of struct vm_struct Kefeng Wang
2022-05-02  9:50   ` Anshuman Khandual
2022-04-29 10:32 ` [PATCH v2 3/5] mm: ioremap: Add arch_ioremap/iounmap() Kefeng Wang
2022-05-19  4:46   ` Anshuman Khandual
2022-05-19  6:24     ` Kefeng Wang [this message]
2022-04-29 10:32 ` [PATCH v2 4/5] arm64: mm: Convert to GENERIC_IOREMAP Kefeng Wang
2022-04-29 23:15   ` kernel test robot
2022-05-02  3:27   ` [PATCH v2 resend " Kefeng Wang
2022-05-16 22:47     ` Catalin Marinas
2022-05-19  5:34     ` Anshuman Khandual
2022-05-19  6:31       ` Kefeng Wang
2022-04-29 10:32 ` [PATCH v2 5/5] arm64: Add HAVE_IOREMAP_PROT support Kefeng Wang
2022-05-16 22:48   ` Catalin Marinas
2022-05-19  5:06   ` Anshuman Khandual
2022-05-10  7:06 ` [PATCH v2 0/5] arm64: Cleanup ioremap() and support ioremap_prot() Kefeng Wang
2022-05-16 22:51 ` Catalin Marinas
2022-05-19  3:37   ` Kefeng Wang

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=06e86db8-0797-1610-48e3-c607cfacf8f7@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=hch@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=will@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