On 10/05/2017 04:45, Steve Rutherford wrote: > Hi KVM, > > I'm currently reading through the new-ish multi-address space support > in KVM. Most of it makes sense, but I'm a bit confused by the handling > of memslots. SMRAM clearly will be its own memslot(s), but when SMM > touches non-SMRAM, is it expected to go through a new SMM-specific set > of memslots that are basically duplicates of the normal address > space's memslots? Yes, the SMM address space is completely separate, and covers both SMRAM and regular memory. In fact SMRAM might not even be its own memslots if userspace coalesces adjacent memslots. In non-SMM you might have two memslots like this for low (<4GB) RAM: 0-0x9ffff (SMRAM at 0xa0000) 0xc0000-0xdf7fffff (TSEG at 0xdf800000) while in SMM a single memslot for 0-0xdfffffff would do. There are a couple slides on multi-AS support at http://www.linux-kvm.org/images/c/ce/03x06-Aspen-Paolo_Bonzini-Securing_secure_boot.pdf. The animations render poorly in PDF, but the LibreOffice .odp is embedded so you can just open the PDF in LibreOffice. Paolo > It seems like this would work and is what is intended, but there might > be something that I'm missing.
