~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/virt/kvm/s390/s390-pv-dump.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/virt/kvm/s390/s390-pv-dump.rst (Version linux-6.12-rc7) and /Documentation/virt/kvm/s390/s390-pv-dump.rst (Version linux-5.19.17)


  1 .. SPDX-License-Identifier: GPL-2.0               
  2                                                   
  3 ===========================================       
  4 s390 (IBM Z) Protected Virtualization dumps       
  5 ===========================================       
  6                                                   
  7 Summary                                           
  8 -------                                           
  9                                                   
 10 Dumping a VM is an essential tool for debuggin    
 11 it. This is especially true when a protected V    
 12 there's no way to access its memory and regist    
 13 while it's running.                               
 14                                                   
 15 However when dumping a protected VM we need to    
 16 confidentiality until the dump is in the hands    
 17 should be the only one capable of analysing it    
 18                                                   
 19 The confidentiality of the VM dump is ensured     
 20 provides an interface to KVM over which encryp    
 21 can be requested. The encryption is based on t    
 22 Communication Key which is the key that's used    
 23 way that the customer is able to decrypt.         
 24                                                   
 25                                                   
 26 Dump process                                      
 27 ------------                                      
 28                                                   
 29 A dump is done in 3 steps:                        
 30                                                   
 31 **Initiation**                                    
 32                                                   
 33 This step initializes the dump process, genera    
 34 and extracts dump keys with which the VM dump     
 35                                                   
 36 **Data gathering**                                
 37                                                   
 38 Currently there are two types of data that can    
 39 the memory and the vcpu state.                    
 40                                                   
 41 The vcpu state contains all the important regi    
 42 point, vector, control and tod/timers of a vcp    
 43 contain incomplete data if a vcpu is dumped wh    
 44 emulated with help of the hypervisor. This is     
 45 in the dump data. For the same reason it is ve    
 46 write out the encrypted vcpu state, but also t    
 47 from the hypervisor.                              
 48                                                   
 49 The memory state is further divided into the e    
 50 metadata comprised of the encryption tweaks an    
 51 encrypted memory can simply be read once it ha    
 52 time of the export does not matter as no re-en    
 53 needed. Memory that has been swapped out and h    
 54 read from the swap and written to the dump tar    
 55 special actions.                                  
 56                                                   
 57 The tweaks / status flags for the exported pag    
 58 from the Ultravisor.                              
 59                                                   
 60 **Finalization**                                  
 61                                                   
 62 The finalization step will provide the data ne    
 63 decrypt the vcpu and memory data and end the d    
 64 step completes successfully a new dump initiat    
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php