linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v4 1/6] libnvdimm/namespace: Make namespace size validation arch dependent
Date: Fri, 24 Jan 2020 13:04:02 +0530	[thread overview]
Message-ID: <5fd11235-5f26-b10a-140f-ef24214c85b1@linux.ibm.com> (raw)
In-Reply-To: <CAPcyv4jcZhQcKr=0OGWc1aZb0OQ1ws2edd-LZMR-EJ_Z2174Sg@mail.gmail.com>

On 1/24/20 11:27 AM, Dan Williams wrote:
> On Mon, Jan 20, 2020 at 6:08 AM Aneesh Kumar K.V
>

....

>>
>> +unsigned long arch_namespace_map_size(void)
>> +{
>> +       return PAGE_SIZE;
>> +}
>> +EXPORT_SYMBOL_GPL(arch_namespace_map_size);
>> +
>> +
>>   static void __cpa_flush_all(void *arg)
>>   {
>>          unsigned long cache = (unsigned long)arg;
>> diff --git a/include/linux/libnvdimm.h b/include/linux/libnvdimm.h
>> index 9df091bd30ba..a3476dbd2656 100644
>> --- a/include/linux/libnvdimm.h
>> +++ b/include/linux/libnvdimm.h
>> @@ -284,4 +284,5 @@ static inline void arch_invalidate_pmem(void *addr, size_t size)
>>   }
>>   #endif
>>
>> +unsigned long arch_namespace_map_size(void);
> 
> This property is more generic than the nvdimm namespace mapping size,
> it's more the fundamental remap granularity that the architecture
> supports. So I would expect this to be defined in core header files.
> Something like:
> 
> diff --git a/include/linux/io.h b/include/linux/io.h
> index a59834bc0a11..58b3b2091dbb 100644
> --- a/include/linux/io.h
> +++ b/include/linux/io.h
> @@ -155,6 +155,13 @@ enum {
>   void *memremap(resource_size_t offset, size_t size, unsigned long flags);
>   void memunmap(void *addr);
> 
> +#ifndef memremap_min_align
> +static inline unsigned int memremap_min_align(void)
> +{
> +       return PAGE_SIZE;
> +}
> +#endif
> +


Should that be memremap_pages_min_align()?

>   /*
>    * On x86 PAT systems we have memory tracking that keeps track of
>    * the allowed mappings on memory ranges. This tracking works for
> 
> ...and then have a definition is asm/io.h like this:
> 
> unsigned int memremap_min_align(void);
> #define memremap_min_align memremap_min_align
> 
> That way only architectures that want to opt out of the default need
> to define something in their local header.
> 

-aneesh
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

  reply	other threads:[~2020-01-24  7:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 14:07 [PATCH v4 0/6] Validating namespace size and start address attributes Aneesh Kumar K.V
2020-01-20 14:07 ` [PATCH v4 1/6] libnvdimm/namespace: Make namespace size validation arch dependent Aneesh Kumar K.V
2020-01-24  5:57   ` Dan Williams
2020-01-24  7:34     ` Aneesh Kumar K.V [this message]
2020-01-24 16:45       ` Dan Williams
2020-01-24 17:07         ` Aneesh Kumar K.V
2020-01-24 18:25           ` Dan Williams
2020-01-26 11:41             ` Aneesh Kumar K.V
2020-01-24 17:08         ` Aneesh Kumar K.V
2020-01-20 14:07 ` [PATCH v4 2/6] libnvdimm/namespace: Validate namespace start addr and size Aneesh Kumar K.V
2020-01-25  1:55   ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 3/6] libnvdimm/namespace: Add arch dependent callback for namespace create time validation Aneesh Kumar K.V
2020-01-25  1:59   ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 4/6] libnvdimm/namespace: Validate namespace size when creating a new namespace Aneesh Kumar K.V
2020-01-25  2:22   ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 5/6] libnvdimm/namespace: Align DPA based on arch restrictions Aneesh Kumar K.V
2020-01-20 14:07 ` [PATCH v4 6/6] libnvdimm/namespace: Expose arch specific supported size align value Aneesh Kumar K.V

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=5fd11235-5f26-b10a-140f-ef24214c85b1@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.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).