All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: x86@kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com,
	tglx@linutronix.de, hpa@zytor.com, JBeulich@suse.com,
	bp@alien8.de
Subject: Re: [PATCH V2 1/1] X86: Hyper-V: Get the local APIC timer frequency from the hypervisor
Date: Wed, 4 Sep 2013 12:40:14 +0300	[thread overview]
Message-ID: <20130904094014.GB7402@redhat.com> (raw)
In-Reply-To: <1378233023-4512-1-git-send-email-kys@microsoft.com>

On Tue, Sep 03, 2013 at 11:30:23AM -0700, K. Y. Srinivasan wrote:
> Hyper-V supports a mechanism for retrieving the local APIC frequency.Use this and bypass
> the calibration code in the kernel. This would allow us to boot the Linux kernel as a
> "modern VM" on Hyper-V where many of the legacy devices (such as PIT) are not emulated.
> 
> I would like to thank Olaf Hering <olaf@aepfle.de>, Jan Beulich <JBeulich@suse.com> and
> H. Peter Anvin <h.peter.anvin@intel.com> for their help in this effort.
> 
> In this version of the patch, I have addressed Jan's comments.
> 
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
>  arch/x86/include/uapi/asm/hyperv.h |   19 +++++++++++++++++++
>  arch/x86/kernel/cpu/mshyperv.c     |   24 ++++++++++++++++++++++++
>  2 files changed, 43 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/x86/include/uapi/asm/hyperv.h b/arch/x86/include/uapi/asm/hyperv.h
> index b80420b..b8f1c01 100644
> --- a/arch/x86/include/uapi/asm/hyperv.h
> +++ b/arch/x86/include/uapi/asm/hyperv.h
> @@ -27,6 +27,19 @@
>  #define HV_X64_MSR_VP_RUNTIME_AVAILABLE		(1 << 0)
>  /* Partition Reference Counter (HV_X64_MSR_TIME_REF_COUNT) available*/
>  #define HV_X64_MSR_TIME_REF_COUNT_AVAILABLE	(1 << 1)
> +
> +/*
> + * There is a single feature flag that signifies the presence of the MSR
> + * that can be used to retrieve both the local APIC Timer frequency as
> + * well as the TSC frequency.
> + */
> +
> +/* Local APIC timer frequency MSR (HV_X64_MSR_APIC_FREQUENCY) is available */
> +#define HV_X64_MSR_APIC_FREQUENCY_AVAILABLE (1 << 11)
> +
> +/* TSC frequency MSR (HV_X64_MSR_TSC_FREQUENCY) is available */
> +#define HV_X64_MSR_TSC_FREQUENCY_AVAILABLE (1 << 11)
> +
>  /*
>   * Basic SynIC MSRs (HV_X64_MSR_SCONTROL through HV_X64_MSR_EOM
>   * and HV_X64_MSR_SINT0 through HV_X64_MSR_SINT15) available
> @@ -136,6 +149,12 @@
>  /* MSR used to read the per-partition time reference counter */
>  #define HV_X64_MSR_TIME_REF_COUNT		0x40000020
>  
> +/* MSR used to retrieve the TSC frequency */
> +#define HV_X64_MSR_TSC_FREQUENCY		0x40000022
> +
You do not use this MSR in the patch, but in general how it suppose to
work during migration if host TSC frequency changes?

> +/* MSR used to retrieve the local APIC timer frequency */
> +#define HV_X64_MSR_APIC_FREQUENCY		0x40000023
> +
>  /* Define the virtual APIC registers */
>  #define HV_X64_MSR_EOI				0x40000070
>  #define HV_X64_MSR_ICR				0x40000071
> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
> index 71a39f3..b3dc639 100644
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -15,6 +15,7 @@
>  #include <linux/clocksource.h>
>  #include <linux/module.h>
>  #include <linux/hardirq.h>
> +#include <linux/efi.h>
>  #include <linux/interrupt.h>
>  #include <asm/processor.h>
>  #include <asm/hypervisor.h>
> @@ -23,6 +24,7 @@
>  #include <asm/desc.h>
>  #include <asm/idle.h>
>  #include <asm/irq_regs.h>
> +#include <asm/i8259.h>
>  
>  struct ms_hyperv_info ms_hyperv;
>  EXPORT_SYMBOL_GPL(ms_hyperv);
> @@ -67,6 +69,8 @@ static struct clocksource hyperv_cs = {
>  
>  static void __init ms_hyperv_init_platform(void)
>  {
> +	u64	hv_lapic_frequency;
> +
>  	/*
>  	 * Extract the features and hints
>  	 */
> @@ -76,6 +80,26 @@ static void __init ms_hyperv_init_platform(void)
>  	printk(KERN_INFO "HyperV: features 0x%x, hints 0x%x\n",
>  	       ms_hyperv.features, ms_hyperv.hints);
>  
> +	if (ms_hyperv.features & HV_X64_MSR_APIC_FREQUENCY_AVAILABLE) {
> +		/*
> +		 * Get the APIC frequency.
> +		 */
> +		rdmsrl(HV_X64_MSR_APIC_FREQUENCY, hv_lapic_frequency);
> +		hv_lapic_frequency /= HZ;
> +		lapic_timer_frequency = hv_lapic_frequency;
> +		printk(KERN_INFO "HyperV: LAPIC Timer Frequency: %#x\n",
> +				lapic_timer_frequency);
> +
> +		/*
> +		 * On Hyper-V, when we are booting off an EFI firmware stack,
> +		 * we do not have many legacy devices including PIC, PIT etc.
> +		 */
> +		if (efi_enabled(EFI_BOOT)) {
> +			printk(KERN_INFO "HyperV: Using null_legacy_pic\n");
> +			legacy_pic = &null_legacy_pic;
> +		}
> +	}
> +
>  	if (ms_hyperv.features & HV_X64_MSR_TIME_REF_COUNT_AVAILABLE)
>  		clocksource_register_hz(&hyperv_cs, NSEC_PER_SEC/100);
>  }
> -- 
> 1.7.4.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
			Gleb.

  parent reply	other threads:[~2013-09-04  9:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 18:30 [PATCH V2 1/1] X86: Hyper-V: Get the local APIC timer frequency from the hypervisor K. Y. Srinivasan
2013-09-04  7:17 ` Jan Beulich
2013-09-04 15:03   ` KY Srinivasan
2013-09-04  9:40 ` Gleb Natapov [this message]
2013-09-04 15:16   ` KY Srinivasan
2013-09-05 14:16     ` Gleb Natapov
2013-09-13  0:06 ` KY Srinivasan
2013-09-13  0:28   ` H. Peter Anvin
2013-09-13  1:43     ` KY Srinivasan
2013-09-13  6:39       ` Jan Beulich
2013-09-13 14:28         ` KY Srinivasan
2013-09-13  9:55       ` Gleb Natapov
2013-09-13 14:28         ` KY Srinivasan
2013-09-17 13:59           ` Gleb Natapov
2013-09-17 19:53             ` KY Srinivasan
2013-09-18  5:43               ` Gleb Natapov
2013-09-23 13:02                 ` KY Srinivasan
2013-09-23 15:50                   ` H. Peter Anvin
2013-09-23 19:23                     ` KY Srinivasan
2013-10-02 23:11                     ` KY Srinivasan
2013-09-27 15:10 ` Olaf Hering
2013-09-27 15:23   ` KY Srinivasan
2013-09-27 15:32     ` Olaf Hering
2013-09-27 15:35       ` KY Srinivasan
2013-10-09 22:50         ` H. Peter Anvin
2013-10-10  0:04           ` KY Srinivasan

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=20130904094014.GB7402@redhat.com \
    --to=gleb@redhat.com \
    --cc=JBeulich@suse.com \
    --cc=apw@canonical.com \
    --cc=bp@alien8.de \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=tglx@linutronix.de \
    --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.