mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	petr@vandrovec.name
Subject: Re: Commit f06e4ec breaks vmware
Date: Mon, 4 Feb 2008 12:51:44 +0100	[thread overview]
Message-ID: <20080204115144.GA17850@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0802020120150.18790@fbirervta.pbzchgretzou.qr>


* Jan Engelhardt <jengelh@computergmbh.de> wrote:

> sad to say, but f06e4ec... breaks booting the kernel in vmware 
> (bisected). Booting just stops after
> 
> 	Checking for 'hlt' instruction...
> 
> commit f06e4ec1c15691b0cfd2397ae32214fa36c90d71
> Author: Ingo Molnar <mingo@elte.hu>
> Date:   Wed Jan 30 13:32:39 2008 +0100
> 
>     x86: read_tsc sync
>     
>     make native_read_tsc() always non-speculative.

could you send us the /proc/cpuinfo data of the guest CPU?

if latest -git still fails, does the patch below solve the problem?

	Ingo

---
 include/asm-x86/system.h |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

Index: linux-x86.q/include/asm-x86/system.h
===================================================================
--- linux-x86.q.orig/include/asm-x86/system.h
+++ linux-x86.q/include/asm-x86/system.h
@@ -407,8 +407,7 @@ void default_idle(void);
  */
 static inline void rdtsc_barrier(void)
 {
-	alternative(ASM_NOP3, "mfence", X86_FEATURE_MFENCE_RDTSC);
-	alternative(ASM_NOP3, "lfence", X86_FEATURE_LFENCE_RDTSC);
+	smp_mb();
 }
 
 #endif

  parent reply	other threads:[~2008-02-04 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 14:11 Jan Engelhardt
2008-02-04  4:19 ` Petr Vandrovec
2008-02-04 11:51 ` Ingo Molnar [this message]
2008-02-04 14:01   ` Jeff Chua
2008-02-04 14:48     ` Ingo Molnar
2008-02-04 14:53     ` Ingo Molnar
2008-02-04 15:30       ` Jeff Chua
2008-02-04 15:36         ` Ingo Molnar
2008-02-04 15:48           ` Jeff Chua
2008-02-05  1:31           ` Zachary Amsden
2008-02-04 14:58   ` Jan Engelhardt

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=20080204115144.GA17850@elte.hu \
    --to=mingo@elte.hu \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petr@vandrovec.name \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®