public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0c29a8ab5843a2f04c070b400e2ccd3de0a4f8a2
Date: Wed, 17 Aug 2016 19:39:43 +0100	[thread overview]
Message-ID: <20160817183943.BC0C41081BA6@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4136 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  0c29a8ab5843a2f04c070b400e2ccd3de0a4f8a2 (commit)
      from  3bf2f1822d654e98d5341c1134479b04edcc8db2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0c29a8ab5843a2f04c070b400e2ccd3de0a4f8a2
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Wed Aug 17 20:37:07 2016 +0200

    kernel: add hyper-v: mark tsc unstable patch
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/linux                                          |  1 +
 ...x-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch | 47 ++++++++++++++++++++++
 2 files changed, 48 insertions(+)
 create mode 100644 src/patches/linux-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch

Difference in files:
diff --git a/lfs/linux b/lfs/linux
index bf71776..cfea069 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -199,6 +199,7 @@ endif
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux/0023-hyperv-Fix-error-return-code-in-netvsc_init_buf.patch
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux/0024-hyperv-Fix-a-bug-in-netvsc_send.patch
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux/0025-Drivers-hv-vmbus-Support-per-channel-driver-state.patch
+	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch
 
 	# fix empty symbol crc's
 	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/linux-genksyms_fix_typeof_handling.patch
diff --git a/src/patches/linux-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch b/src/patches/linux-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch
new file mode 100644
index 0000000..d12f46b
--- /dev/null
+++ b/src/patches/linux-hyperv_Mark_the_Hyoer-V_TSC_as_unstable.patch
@@ -0,0 +1,47 @@
+From 88c9281a9fba67636ab26c1fd6afbc78a632374f Mon Sep 17 00:00:00 2001
+From: Vitaly Kuznetsov <vkuznets(a)redhat.com>
+Date: Wed, 19 Aug 2015 09:54:24 -0700
+Subject: x86/hyperv: Mark the Hyper-V TSC as unstable
+
+The Hyper-V top-level functional specification states, that
+"algorithms should be resilient to sudden jumps forward or
+backward in the TSC value", this means that we should consider
+TSC as unstable. In some cases tsc tests are able to detect the
+instability, it was detected in 543 out of 646 boots in my
+testing:
+
+ Measured 6277 cycles TSC warp between CPUs, turning off TSC clock.
+ tsc: Marking TSC unstable due to check_tsc_sync_source failed
+
+This is, however, just a heuristic. On Hyper-V platform there
+are two good clocksources: MSR-based hyperv_clocksource and
+recently introduced TSC page.
+
+Signed-off-by: Vitaly Kuznetsov <vkuznets(a)redhat.com>
+Cc: Haiyang Zhang <haiyangz(a)microsoft.com>
+Cc: K. Y. Srinivasan <kys(a)microsoft.com>
+Cc: Linus Torvalds <torvalds(a)linux-foundation.org>
+Cc: Peter Zijlstra <peterz(a)infradead.org>
+Cc: Thomas Gleixner <tglx(a)linutronix.de>
+Cc: devel(a)linuxdriverproject.org
+Link: http://lkml.kernel.org/r/1440003264-9949-1-git-send-email-vkuznets(a)redhat.com
+Signed-off-by: Ingo Molnar <mingo(a)kernel.org>
+---
+ arch/x86/kernel/cpu/mshyperv.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
+index aad4bd8..6fd023d 100644
+--- a/arch/x86/kernel/cpu/mshyperv.c
++++ b/arch/x86/kernel/cpu/mshyperv.c
+@@ -141,6 +141,7 @@ static void __init ms_hyperv_init_platform(void)
+ 	no_timer_check = 1;
+ #endif
+ 
++	mark_tsc_unstable("running on Hyper-V");
+ }
+ 
+ const __refconst struct hypervisor_x86 x86_hyper_ms_hyperv = {
+-- 
+cgit v0.12
+


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2016-08-17 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160817183943.BC0C41081BA6@git01.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox