Re: [PATCH v4 2/2] KVM: PPC: Implement H_SVM_INIT_ABORT hcall

2020-01-07 Thread Ram Pai
On Mon, Jan 06, 2020 at 06:02:37PM -0800, Sukadev Bhattiprolu wrote: > Ram Pai [linux...@us.ibm.com] wrote: > > > > One small comment.. H_STATE is a better return code than H_UNSUPPORTED. > > > > Here is the updated patch - we now return H_STATE if the abort call is > made after the VM has gone

Re: [PATCH v4 2/2] KVM: PPC: Implement H_SVM_INIT_ABORT hcall

2020-01-06 Thread Sukadev Bhattiprolu
Ram Pai [linux...@us.ibm.com] wrote: > > One small comment.. H_STATE is a better return code than H_UNSUPPORTED. > Here is the updated patch - we now return H_STATE if the abort call is made after the VM has gone secure. --- >From 73fe1fa5aff2829f2fae6a339169e56dc0bbae06 Mon Sep 17 00:00:00 2001

Re: [PATCH v4 2/2] KVM: PPC: Implement H_SVM_INIT_ABORT hcall

2020-01-03 Thread Ram Pai
On Thu, Dec 19, 2019 at 01:51:46PM -0800, Sukadev Bhattiprolu wrote: > Implement the H_SVM_INIT_ABORT hcall which the Ultravisor can use to > abort an SVM after it has issued the H_SVM_INIT_START and before the > H_SVM_INIT_DONE hcalls. This hcall could be used when Ultravisor > encounters

[PATCH v4 2/2] KVM: PPC: Implement H_SVM_INIT_ABORT hcall

2019-12-19 Thread Sukadev Bhattiprolu
Implement the H_SVM_INIT_ABORT hcall which the Ultravisor can use to abort an SVM after it has issued the H_SVM_INIT_START and before the H_SVM_INIT_DONE hcalls. This hcall could be used when Ultravisor encounters security violations or other errors when starting an SVM. Note that this hcall is