On Thu, Mar 19, 2020 at 08:46:36AM -0700, Andy Lutomirski wrote: > This can't possibly end well. Maybe have a little percpu list of > GHCBs and make sure there are enough for any possible nesting? Yeah, it is not entirely robust yet. Without NMI nesting the number of possible #VC nesting levels should be limited. At least one backup GHCB pre-allocated is probably a good idea. > Also, I admit confusion. Isn't the GHCB required to be unencrypted? > How does that work with kzalloc()? Yes, but the kzalloc'ed ghcb is just the backup space for the real GHCB, which is mapped unencrypted. The contents of the unencrypted GHCB is copied to the backup and restored on return, so that the interrupted #VC handler finds the GHCB unmodified. Regards, Joerg
