All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
	kvm@vger.kernel.org, x86@kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	"Stephen Hemminger" <sthemmin@microsoft.com>,
	"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Mohammed Gamal" <mmorsy@redhat.com>,
	"Cathy Avery" <cavery@redhat.com>,
	"Roman Kagan" <rkagan@virtuozzo.com>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V
Date: Fri, 15 Dec 2017 10:01:06 +0100	[thread overview]
Message-ID: <e9d2f20a-178f-a42e-d1e3-7396c04315bb@redhat.com> (raw)
In-Reply-To: <20171213150945.24054-1-vkuznets@redhat.com>

On 13/12/2017 16:09, Vitaly Kuznetsov wrote:
> Currently, KVM passes PVCLOCK_TSC_STABLE_BIT to its guests when running in
> so called 'masterclock' mode and this is only possible when the clocksource
> on the host is TSC. When running nested on Hyper-V we're using a different
> clocksource in L1 (Hyper-V TSC Page) which can actually be used for
> masterclock. This series brings the required support.
> 
> Making KVM work with TSC page clocksource is relatively easy, it is done in
> PATCH 5 of the series. All the rest is required to support L1 migration
  ^^^^^^^

Patch 6. :)

> when TSC frequency changes, we use a special feature from Hyper-V to do
> the job.

Patches 5-7 are

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

I would appreciate if the Hyper-V folks can provide a topic branch to be
merged in both HV and KVM trees.

Thanks,

Paolo

> Vitaly Kuznetsov (7):
>   x86/hyper-v: check for required priviliges in hyperv_init()
>   x86/hyper-v: add a function to read both TSC and TSC page value
>     simulateneously
>   x86/hyper-v: reenlightenment notifications support
>   x86/hyper-v: redirect reenlightment notifications on CPU offlining
>   x86/irq: Count Hyper-V reenlightenment interrupts
>   x86/kvm: pass stable clocksource to guests when running nested on
>     Hyper-V
>   x86/kvm: support Hyper-V reenlightenment
> 
>  arch/x86/entry/entry_32.S          |   3 +
>  arch/x86/entry/entry_64.S          |   3 +
>  arch/x86/hyperv/hv_init.c          | 133 ++++++++++++++++++++++++++++++++++-
>  arch/x86/include/asm/hardirq.h     |   3 +
>  arch/x86/include/asm/irq_vectors.h |   7 +-
>  arch/x86/include/asm/mshyperv.h    |  32 +++++++--
>  arch/x86/include/uapi/asm/hyperv.h |  27 ++++++++
>  arch/x86/kernel/cpu/mshyperv.c     |   6 ++
>  arch/x86/kernel/irq.c              |   9 +++
>  arch/x86/kvm/x86.c                 | 138 ++++++++++++++++++++++++++++++-------
>  10 files changed, 329 insertions(+), 32 deletions(-)
> 

  parent reply	other threads:[~2017-12-15  9:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 15:09 [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Vitaly Kuznetsov
2017-12-13 15:09 ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 1/7] x86/hyper-v: check for required priviliges in hyperv_init() Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:32   ` Thomas Gleixner
2018-01-14 20:32     ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously Vitaly Kuznetsov
2018-01-14 20:35   ` Thomas Gleixner
2018-01-14 20:35     ` Thomas Gleixner
2018-01-15 10:45     ` Vitaly Kuznetsov
2018-01-15 10:45       ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 3/7] x86/hyper-v: reenlightenment notifications support Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:42   ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2018-01-14 20:44   ` Thomas Gleixner
2018-01-15 10:44     ` Vitaly Kuznetsov
2018-01-15 10:44       ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 5/7] x86/irq: Count Hyper-V reenlightenment interrupts Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 7/7] x86/kvm: support Hyper-V reenlightenment Vitaly Kuznetsov
2017-12-13 15:09   ` Vitaly Kuznetsov
2017-12-15  9:01 ` Paolo Bonzini [this message]
2017-12-15  9:30   ` [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Vitaly Kuznetsov
2018-01-03 14:57     ` Vitaly Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e9d2f20a-178f-a42e-d1e3-7396c04315bb@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=cavery@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mmorsy@redhat.com \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.com \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.