lkml.org 
[lkml]   [2018]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH RFC 2/2] KVM: s390: introduce and use KVM_REQ_VSIE_RESTART
    From
    Date
    On 07.08.2018 14:51, David Hildenbrand wrote:
    > When we change the crycb (or execution controls), we also have to make sure
    > that the vSIE shadow datastructures properly consider the changed
    > values before rerunning the vSIE. We can achieve that by simply using a
    > VCPU request now.
    >
    > This has to be a synchronous request (== handled before entering the
    > (v)SIE again).
    >
    > The request will make sure that the vSIE handler is left, and that the
    > request will be processed (NOP), therefore forcing a reload of all
    > vSIE data (including rebuilding the crycb) when re-entering the vSIE
    > interception handler the next time.
    >
    > Signed-off-by: David Hildenbrand <david@redhat.com>

    Reviewed-by: Janosch Frank <frankja@linux.ibm.com>

    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2018-08-09 07:39    [W:2.093 / U:0.312 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site