From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Zachary Amsden <zach@vmware.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18 is problematic in VMware
Date: Thu, 2 Nov 2006 10:13:33 +0200 [thread overview]
Message-ID: <200611021013.38701.caglar@pardus.org.tr> (raw)
In-Reply-To: <45463B7D.8050002@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
30 Eki 2006 Pts 19:50 tarihinde, Zachary Amsden şunları yazmıştı:
> > * Checking if this processor honours the WP bit even in supervisor
> > mode... Ok. * Checking 'hlt' instruction... OK.
> >
> > What's with that?
>
> Thanks. It is perhaps the jiffies calibration taking a while because of
> the precise timing loop. Are you reasonably confident that it is a
> regression in performance over 2.6.17? The boot sequence is pretty
> complicated, and a lot of it is difficult / slow to virtualize, so it
> could just be alternate timing makes the boot output appear to stall,
> when in fact the raw time is still about the same. I will run some
> experiments.
This is the part of the same problem with my previous report ( [RFC] Avoid PIT
SMP lockups thread), and im sure none the previous kernels have that problem.
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-11-02 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 9:55 2.6.18 is problematic in VMware Jan Engelhardt
2006-10-30 17:50 ` Zachary Amsden
2006-10-31 7:59 ` Jan Engelhardt
2006-10-31 14:06 ` Mark Lord
2006-10-31 17:20 ` Jan Engelhardt
2006-11-01 2:33 ` Zachary Amsden
2006-11-03 8:07 ` Jan Engelhardt
2006-11-02 8:21 ` S.Çağlar Onur
2006-11-02 8:13 ` S.Çağlar Onur [this message]
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=200611021013.38701.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.com \
/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