linux-kernel - Re: [RFC] KVM: x86: Support KVM VMs sharing SEV context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <69004ca1-93a7-6a7e-b349-05f857756334@redhat.com>
Date:   Mon, 15 Mar 2021 18:29:59 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Tobin Feldman-Fitzthum <tobin@...ux.ibm.com>, natet@...gle.com
Cc:     Dov Murik <dovmurik@...ux.vnet.ibm.com>,
        Tom Lendacky <thomas.lendacky@....com>, x86@...nel.org,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        srutherford@...gle.com, seanjc@...gle.com, rientjes@...gle.com,
        Brijesh Singh <brijesh.singh@....com>,
        Ashish Kalra <ashish.kalra@....com>,
        Laszlo Ersek <lersek@...hat.com>,
        James Bottomley <jejb@...ux.ibm.com>,
        Hubertus Franke <frankeh@...ibm.com>,
        Tobin Feldman-Fitzthum <tobin@....com>
Subject: Re: [RFC] KVM: x86: Support KVM VMs sharing SEV context

On 15/03/21 18:05, Tobin Feldman-Fitzthum wrote:
>>
>> I can answer this part.  I think this will actually be simpler than 
>> with auxiliary vCPUs.  There will be a separate pair of VM+vCPU file 
>> descriptors within the same QEMU process, and some code to set up the 
>> memory map using KVM_SET_USER_MEMORY_REGION.
>>
>> However, the code to run this VM will be very small as the VM does not 
>> have to do MMIO, interrupts, live migration (of itself), etc.  It just 
>> starts up and communicates with QEMU using a mailbox at a 
>> predetermined address.
> 
> We've been starting up our Migration Handler via OVMF. I'm not sure if 
> this would work with a minimal setup in QEMU.

Yeah, the way to start up the migration handler would be completely 
different, you'd have to do so very early (probably SEC).

Paolo