MIME-Version: 1.0
In-Reply-To: <f93105c1-0d6f-f9d4-fc43-31efae1c9aeb@virtuozzo.com>
References: <1501684690-211093-1-git-send-email-dplotnikov@virtuozzo.com>
 <CALAqxLVngARqG4g8URMQGQtZec_p5NVP7hFXQGS6+JWp74FVMA@mail.gmail.com>
 <b913b3b2-b3bb-348a-4069-c251a22233cd@redhat.com> <f93105c1-0d6f-f9d4-fc43-31efae1c9aeb@virtuozzo.com>
From: John Stultz <john.stultz@linaro.org>
Date: Tue, 22 Aug 2017 12:50:06 -0700
Message-ID: <CALAqxLWGf6BAdji=rqKPnyvFzzUQscA5rXU8SY4RcWXymyVL1Q@mail.gmail.com>
Subject: Re: [PATCH v4 00/10] make L2's kvm-clock stable, get rid of
 pvclock_gtod_copy in KVM
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Radim Krcmar <rkrcmar@redhat.com>,
        kvm list <kvm@vger.kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
        lkml <linux-kernel@vger.kernel.org>, "x86@kernel.org" <x86@kernel.org>,
        rkagan@virtuozzo.com, den@virtuozzo.com,
        Marcelo Tosatti <mtosatti@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 771
Lines: 24

On Mon, Aug 21, 2017 at 1:40 AM, Denis Plotnikov
<dplotnikov@virtuozzo.com> wrote:
> ping!
>

I still don't feel my questions have been well answered. Its really
not clear to me why, in order to allow the level-2 guest to use a vdso
that the answer is to export more data through the entire stack rather
then to make the kvmclock to be usable from the vsyscall.

So far for a problem statement, all I've got is:
"However, when using nested virtualization you have

        L0: bare-metal hypervisor (uses TSC)
        L1: nested hypervisor (uses kvmclock, can use vsyscall)
        L2: nested guest

and L2 cannot use vsyscall because it is not using the TSC."

Which is a start but doesn't really make it clear why the proposed
solution is best/necessary.

thanks
-john