From: Michael Ellerman <ellerman@au1.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
sbhat@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, linux-nvdimm@lists.01.org
Cc: linux-doc@vger.kernel.org, vaibhav@linux.ibm.com
Subject: Re: [PATCH v3] powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall
Date: Wed, 31 Mar 2021 21:20:36 +1100 [thread overview]
Message-ID: <87zgyjwrnv.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87mtul6xzj.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Shivaprasad G Bhat <sbhat@linux.ibm.com> writes:
>
>> Add support for ND_REGION_ASYNC capability if the device tree
>> indicates 'ibm,hcall-flush-required' property in the NVDIMM node.
>> Flush is done by issuing H_SCM_FLUSH hcall to the hypervisor.
>>
>> If the flush request failed, the hypervisor is expected to
>> to reflect the problem in the subsequent nvdimm H_SCM_HEALTH call.
>>
>> This patch prevents mmap of namespaces with MAP_SYNC flag if the
>> nvdimm requires an explicit flush[1].
>>
>> References:
>> [1] https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/ndctl.py.data/map_sync.c
>
>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Do we need an ack from nvdimm folks on this?
Or is it entirely powerpc internal (seems like it from the diffstat)?
cheers
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <ellerman@au1.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
sbhat@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, linux-nvdimm@lists.01.org
Cc: linux-doc@vger.kernel.org, vaibhav@linux.ibm.com
Subject: Re: [PATCH v3] powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall
Date: Wed, 31 Mar 2021 21:20:36 +1100 [thread overview]
Message-ID: <87zgyjwrnv.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87mtul6xzj.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Shivaprasad G Bhat <sbhat@linux.ibm.com> writes:
>
>> Add support for ND_REGION_ASYNC capability if the device tree
>> indicates 'ibm,hcall-flush-required' property in the NVDIMM node.
>> Flush is done by issuing H_SCM_FLUSH hcall to the hypervisor.
>>
>> If the flush request failed, the hypervisor is expected to
>> to reflect the problem in the subsequent nvdimm H_SCM_HEALTH call.
>>
>> This patch prevents mmap of namespaces with MAP_SYNC flag if the
>> nvdimm requires an explicit flush[1].
>>
>> References:
>> [1] https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/ndctl.py.data/map_sync.c
>
>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Do we need an ack from nvdimm folks on this?
Or is it entirely powerpc internal (seems like it from the diffstat)?
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <ellerman@au1.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
sbhat@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, linux-nvdimm@lists.01.org
Cc: vaibhav@linux.ibm.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall
Date: Wed, 31 Mar 2021 21:20:36 +1100 [thread overview]
Message-ID: <87zgyjwrnv.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87mtul6xzj.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Shivaprasad G Bhat <sbhat@linux.ibm.com> writes:
>
>> Add support for ND_REGION_ASYNC capability if the device tree
>> indicates 'ibm,hcall-flush-required' property in the NVDIMM node.
>> Flush is done by issuing H_SCM_FLUSH hcall to the hypervisor.
>>
>> If the flush request failed, the hypervisor is expected to
>> to reflect the problem in the subsequent nvdimm H_SCM_HEALTH call.
>>
>> This patch prevents mmap of namespaces with MAP_SYNC flag if the
>> nvdimm requires an explicit flush[1].
>>
>> References:
>> [1] https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/ndctl.py.data/map_sync.c
>
>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Do we need an ack from nvdimm folks on this?
Or is it entirely powerpc internal (seems like it from the diffstat)?
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <ellerman@au1.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.ibm.com>,
sbhat@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, linux-nvdimm@lists.01.org
Cc: linux-doc@vger.kernel.org, vaibhav@linux.ibm.com
Subject: Re: [PATCH v3] powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall
Date: Wed, 31 Mar 2021 10:20:36 +0000 [thread overview]
Message-ID: <87zgyjwrnv.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87mtul6xzj.fsf@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> Shivaprasad G Bhat <sbhat@linux.ibm.com> writes:
>
>> Add support for ND_REGION_ASYNC capability if the device tree
>> indicates 'ibm,hcall-flush-required' property in the NVDIMM node.
>> Flush is done by issuing H_SCM_FLUSH hcall to the hypervisor.
>>
>> If the flush request failed, the hypervisor is expected to
>> to reflect the problem in the subsequent nvdimm H_SCM_HEALTH call.
>>
>> This patch prevents mmap of namespaces with MAP_SYNC flag if the
>> nvdimm requires an explicit flush[1].
>>
>> References:
>> [1] https://github.com/avocado-framework-tests/avocado-misc-tests/blob/master/memory/ndctl.py.data/map_sync.c
>
>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Do we need an ack from nvdimm folks on this?
Or is it entirely powerpc internal (seems like it from the diffstat)?
cheers
next prev parent reply other threads:[~2021-03-31 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 17:36 [PATCH v3] powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall Shivaprasad G Bhat
2021-03-29 17:36 ` Shivaprasad G Bhat
2021-03-29 17:36 ` Shivaprasad G Bhat
2021-03-29 17:36 ` Shivaprasad G Bhat
2021-03-30 4:56 ` Aneesh Kumar K.V
2021-03-30 4:56 ` Aneesh Kumar K.V
2021-03-30 4:56 ` Aneesh Kumar K.V
2021-03-30 4:56 ` Aneesh Kumar K.V
2021-03-31 10:20 ` Michael Ellerman [this message]
2021-03-31 10:20 ` Michael Ellerman
2021-03-31 10:20 ` Michael Ellerman
2021-03-31 10:20 ` Michael Ellerman
2021-04-05 3:47 ` Aneesh Kumar K.V
2021-04-05 3:59 ` Aneesh Kumar K.V
2021-04-05 3:47 ` Aneesh Kumar K.V
2021-04-05 3:47 ` Aneesh Kumar K.V
2021-04-13 14:13 ` Vaibhav Jain
2021-04-13 14:25 ` Vaibhav Jain
2021-04-13 14:13 ` Vaibhav Jain
2021-04-14 5:20 ` Aneesh Kumar K.V
2021-04-14 5:32 ` Aneesh Kumar K.V
2021-04-14 5:20 ` Aneesh Kumar K.V
2021-04-14 9:21 ` Vaibhav Jain
2021-04-14 9:33 ` Vaibhav Jain
2021-04-14 9:21 ` Vaibhav Jain
2021-04-19 3:59 ` Michael Ellerman
2021-04-19 3:59 ` Michael Ellerman
2021-04-19 3:59 ` Michael Ellerman
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=87zgyjwrnv.fsf@mpe.ellerman.id.au \
--to=ellerman@au1.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sbhat@linux.ibm.com \
--cc=sbhat@linux.vnet.ibm.com \
--cc=vaibhav@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.