On Tue, Aug 17, 2021 at 3:57 PM James Bottomley wrote:
> Realistically, migration is becoming a royal pain, not just for
> confidential computing, but for virtual functions in general. I really
> think we should look at S3 suspend, where we shut down the drivers and
> then reattach on S3 resume a
On Tue, Aug 17, 2021 at 1:50 PM Tobin Feldman-Fitzthum
wrote:
>
>
> On 8/17/21 12:32 PM, Paolo Bonzini wrote:
> > There's three possibilities for this:
> >
> > 1) the easy one: the bottom 4G of guest memory are mapped in the
> > mirror VM 1:1. The ram_addr_t-based addresses are shifted by either
On Tue, Aug 17, 2021 at 9:32 AM Paolo Bonzini wrote:
>
> On 17/08/21 01:53, Steve Rutherford wrote:
> > Separately, I'm a little weary of leaving the migration helper mapped
> > into the shared address space as writable.
>
> A related question here is what the API sh
On Mon, Aug 16, 2021 at 6:37 AM Ashish Kalra wrote:
>
> From: Ashish Kalra
>
> This is an RFC series for Mirror VM support that are
> essentially secondary VMs sharing the encryption context
> (ASID) with a primary VM. The patch-set creates a new
> VM and shares the primary VM's encryption contex
Do you mean MiB/s, MB/s or Mb/s? Since you are talking about network
speeds, sometimes these get conflated.
I'm guessing you mean MB/s since you are also using 4kb for page size.
On Wed, Apr 24, 2019 at 2:32 PM Singh, Brijesh
wrote:
>
>
> On 4/24/19 2:15 PM, Steve Rutherford wro
On Wed, Apr 24, 2019 at 9:10 AM Singh, Brijesh wrote:
>
> The series add support for AMD SEV guest live migration commands. To protect
> the
> confidentiality of an SEV protected guest memory while in transit we need to
> use the SEV commands defined in SEV API spec [1].
>
> SEV guest VMs have th
