public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH RFC 0/2] KVM: s390: vsie: protect from VCPUS modifying the SCB
@ 2018-01-16 17:15 David Hildenbrand
  2018-01-16 17:15 ` [PATCH RFC 1/2] KVM: s390 vsie: use READ_ONCE to access some SCB fields David Hildenbrand
  2018-01-16 17:15 ` [PATCH RFC 2/2] KVM: s390: vsie: store guest addresses of satellite blocks in vsie_page David Hildenbrand
  0 siblings, 2 replies; 7+ messages in thread
From: David Hildenbrand @ 2018-01-16 17:15 UTC (permalink / raw)
  To: KVM; +Cc: linux-s390, Christian Borntraeger, Cornelia Huck

As the (nested) SCB is just guest memory, other VCPUs can try to modify it
while we are building our shadow SCB.

Let's avoid unpredictable behavior by adding some READ_ONCE and refactoring
unpinning of satellite control blocks.

Compile tested only for now.

David Hildenbrand (2):
  KVM: s390 vsie: use READ_ONCE to access some SCB fields
  KVM: s390: vsie: store guest addresses of satellite blocks in
    vsie_page

 arch/s390/kvm/vsie.c | 87 ++++++++++++++++++++++++++++++++--------------------
 1 file changed, 53 insertions(+), 34 deletions(-)

-- 
2.14.3

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2018-01-23 12:29 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-16 17:15 [PATCH RFC 0/2] KVM: s390: vsie: protect from VCPUS modifying the SCB David Hildenbrand
2018-01-16 17:15 ` [PATCH RFC 1/2] KVM: s390 vsie: use READ_ONCE to access some SCB fields David Hildenbrand
2018-01-23 11:15   ` Christian Borntraeger
2018-01-23 12:26   ` Cornelia Huck
2018-01-16 17:15 ` [PATCH RFC 2/2] KVM: s390: vsie: store guest addresses of satellite blocks in vsie_page David Hildenbrand
2018-01-23 11:18   ` Christian Borntraeger
2018-01-23 12:29   ` Cornelia Huck

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox