Re: [PATCH 2/2] powerpc/nvdimm: use H_SCM_QUERY hcall on H_OVERLAP error

2019-08-29 Thread Oliver O'Halloran
On Thu, Aug 29, 2019 at 6:21 PM Aneesh Kumar K.V wrote: > > On 8/29/19 1:29 PM, Oliver O'Halloran wrote: > > On Thu, Aug 29, 2019 at 4:34 PM Aneesh Kumar K.V > > wrote: > >> > >> Right now we force an unbind of SCM memory at drcindex on H_OVERLAP error. > >> This really slows down operations like

Re: [PATCH 2/2] powerpc/nvdimm: use H_SCM_QUERY hcall on H_OVERLAP error

2019-08-29 Thread Aneesh Kumar K.V
On 8/29/19 1:29 PM, Oliver O'Halloran wrote: On Thu, Aug 29, 2019 at 4:34 PM Aneesh Kumar K.V wrote: Right now we force an unbind of SCM memory at drcindex on H_OVERLAP error. This really slows down operations like kexec where we get the H_OVERLAP error because we don't go through a full hyper

Re: [PATCH 2/2] powerpc/nvdimm: use H_SCM_QUERY hcall on H_OVERLAP error

2019-08-29 Thread Oliver O'Halloran
On Thu, Aug 29, 2019 at 4:34 PM Aneesh Kumar K.V wrote: > > Right now we force an unbind of SCM memory at drcindex on H_OVERLAP error. > This really slows down operations like kexec where we get the H_OVERLAP > error because we don't go through a full hypervisor re init. Maybe we should be unbind

[PATCH 2/2] powerpc/nvdimm: use H_SCM_QUERY hcall on H_OVERLAP error

2019-08-28 Thread Aneesh Kumar K.V
Right now we force an unbind of SCM memory at drcindex on H_OVERLAP error. This really slows down operations like kexec where we get the H_OVERLAP error because we don't go through a full hypervisor re init. H_OVERLAP error for a H_SCM_BIND_MEM hcall indicates that SCM memory at drc index is alrea