On Fri, Dec 11, 2020 at 04:03:36PM +0530, Bharata B Rao wrote: > On Mon, Oct 19, 2020 at 04:56:41PM +0530, Bharata B Rao wrote: > > Implements H_RPT_INVALIDATE hcall and supports only nested case > > currently. > > > > A KVM capability KVM_CAP_RPT_INVALIDATE is added to indicate the > > support for this hcall. > > As Paul mentioned in the thread, this hcall does both process scoped > invalidations and partition scoped invalidations for L2 guest. > I am adding KVM_CAP_RPT_INVALIDATE capability with only partition > scoped invalidations (nested case) implemented in the hcall as we > don't see the need for KVM to implement process scoped invalidation > function as KVM may never run with LPCR[GTSE]=0. > > I am wondering if enabling the capability with only partial > implementation of the hcall is the correct thing to do. In future > if we ever want process scoped invalidations support in this hcall, > we may not be able to differentiate the availability of two functions > cleanly from QEMU. Yeah, it's not ideal. > So does it make sense to implement the process scoped invalidation > function also now itself even if it is not going to be used in > KVM? That might be a good idea, if it's not excessively difficult. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
