From: Vaibhav Jain <vaibhav@linux.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v3 2/3] powerpc/papr_scm: Update drc_pmem_unbind() to use H_SCM_UNBIND_ALL
Date: Thu, 27 Jun 2019 20:10:20 +0530 [thread overview]
Message-ID: <87o92jum5n.fsf@vajain21.in.ibm.com> (raw)
In-Reply-To: <4a460995-f7c5-22bf-028e-628d984dce96@linux.ibm.com>
Thanks for reviewing this patch Aneesh,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> On 6/26/19 7:34 PM, Vaibhav Jain wrote:
>> The new hcall named H_SCM_UNBIND_ALL has been introduce that can
>> unbind all or specific scm memory assigned to an lpar. This is
>> more efficient than using H_SCM_UNBIND_MEM as currently we don't
>> support partial unbind of scm memory.
>>
>> Hence this patch proposes following changes to drc_pmem_unbind():
>>
>> * Update drc_pmem_unbind() to replace hcall H_SCM_UNBIND_MEM to
>> H_SCM_UNBIND_ALL.
>>
>> * Update drc_pmem_unbind() to handles cases when PHYP asks the guest
>> kernel to wait for specific amount of time before retrying the
>> hcall via the 'LONG_BUSY' return value.
>>
>> * Ensure appropriate error code is returned back from the function
>> in case of an error.
>>
>> Reviewed-by: Oliver O'Halloran <oohall@gmail.com>
>> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
>> ---
>> Change-log:
>>
>> v3:
>> * Fixed a build warning reported by kbuild-robot.
>> * Updated patch description to put emphasis on 'scm memory' instead of
>> 'scm drc memory blocks' as for phyp there is a stark difference
>> between how drc are managed for scm memory v/s regular memory. [Oliver]
>>
>> v2:
>> * Added a dev_dbg when unbind operation succeeds [Oliver]
>> * Changed type of variable 'rc' to int64_t [Oliver]
>> * Removed the code that was logging a warning in case bind operation
>> takes >1-seconds [Oliver]
>> * Spinned off changes to hvcall.h as a separate patch. [Oliver]
>> ---
>> arch/powerpc/platforms/pseries/papr_scm.c | 29 +++++++++++++++++------
>> 1 file changed, 22 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/powerpc/platforms/pseries/papr_scm.c b/arch/powerpc/platforms/pseries/papr_scm.c
>> index 96c53b23e58f..c01a03fd3ee7 100644
>> --- a/arch/powerpc/platforms/pseries/papr_scm.c
>> +++ b/arch/powerpc/platforms/pseries/papr_scm.c
>> @@ -11,6 +11,7 @@
>> #include <linux/sched.h>
>> #include <linux/libnvdimm.h>
>> #include <linux/platform_device.h>
>> +#include <linux/delay.h>
>>
>> #include <asm/plpar_wrappers.h>
>>
>> @@ -77,22 +78,36 @@ static int drc_pmem_bind(struct papr_scm_priv *p)
>> static int drc_pmem_unbind(struct papr_scm_priv *p)
>> {
>> unsigned long ret[PLPAR_HCALL_BUFSIZE];
>> - uint64_t rc, token;
>> + uint64_t token = 0;
>> + int64_t rc;
>>
>> - token = 0;
>> + dev_dbg(&p->pdev->dev, "unbind drc %x\n", p->drc_index);
>>
>> - /* NB: unbind has the same retry requirements mentioned above */
>> + /* NB: unbind has the same retry requirements as drc_pmem_bind() */
>> do {
>> - rc = plpar_hcall(H_SCM_UNBIND_MEM, ret, p->drc_index,
>> - p->bound_addr, p->blocks, token);
>> +
>> + /* Unbind of all SCM resources associated with drcIndex */
>> + rc = plpar_hcall(H_SCM_UNBIND_ALL, ret, H_UNBIND_SCOPE_DRC,
>> + p->drc_index, token);
>> token = ret[0];
>> - cond_resched();
>> +
>> + /* Check if we are stalled for some time */
>> + if (H_IS_LONG_BUSY(rc)) {
>> + msleep(get_longbusy_msecs(rc));
>> + rc = H_BUSY;
>> + } else if (rc == H_BUSY) {
>> + cond_resched();
>> + }
>> +
>> } while (rc == H_BUSY);
>>
>> if (rc)
>> dev_err(&p->pdev->dev, "unbind error: %lld\n", rc);
>> + else
>> + dev_dbg(&p->pdev->dev, "unbind drc %x complete\n",
>> + p->drc_index);
>>
> Can we add p->drc_index as part of these messages? Also s/%x/0x%x ?
the scm platform device has the name of the form
"ibm,persistent-memory:ibm,pmemory@44100002" which also contains the
drc_index. So i think printing it again in this message would be
redundant.
>
>
>> - return !!rc;
>> + return rc == H_SUCCESS ? 0 : -ENXIO;
>> }
>>
> The error -ENXIO is confusing. Can we keep the HCALL error as return for
> this? We don't check error from this. If we can't take any action based
> on the return. Then may be make it void?
>
Wanted to keep the behaviour of this function symmetric to
drc_pmem_bind() which when updated in the next patch returns a kernel
error code instead of hcall error.
Agree that we arent using the return
value of this function right now but this may change in the future.
>
>> static int papr_scm_meta_get(struct papr_scm_priv *p,
>>
>
>
> -aneesh
--
Vaibhav Jain <vaibhav@linux.ibm.com>
Linux Technology Center, IBM India Pvt. Ltd.
next prev parent reply other threads:[~2019-06-27 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 14:04 [PATCH v3 0/3] powerpc/papr_scm: Workaround for failure of drc bind after kexec Vaibhav Jain
2019-06-26 14:04 ` [PATCH v3 1/3] powerpc/pseries: Update SCM hcall op-codes in hvcall.h Vaibhav Jain
2019-06-26 16:53 ` Aneesh Kumar K.V
2019-06-27 1:10 ` Oliver O'Halloran
2019-06-28 3:39 ` Michael Ellerman
2019-06-28 4:36 ` Oliver O'Halloran
2019-06-29 11:30 ` Michael Ellerman
2019-06-29 16:09 ` Vaibhav Jain
2019-06-26 14:04 ` [PATCH v3 2/3] powerpc/papr_scm: Update drc_pmem_unbind() to use H_SCM_UNBIND_ALL Vaibhav Jain
2019-06-26 15:41 ` Aneesh Kumar K.V
2019-06-27 14:40 ` Vaibhav Jain [this message]
2019-06-26 14:04 ` [PATCH v3 3/3] powerpc/papr_scm: Force a scm-unbind if initial scm-bind fails Vaibhav Jain
2019-06-26 16:58 ` Aneesh Kumar K.V
2019-06-27 1:41 ` Oliver O'Halloran
2019-06-27 2:56 ` Aneesh Kumar K.V
2019-06-27 3:39 ` Oliver O'Halloran
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=87o92jum5n.fsf@vajain21.in.ibm.com \
--to=vaibhav@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.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 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).