public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Paul Jackson <pj@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ia64 SN2 - migration costs: 1) nearly zero 2) BUG 3) repeated
Date: Sun, 13 Nov 2005 08:17:16 +0100	[thread overview]
Message-ID: <20051113071716.GA31075@elte.hu> (raw)
In-Reply-To: <20051112144949.3b331aa1.pj@sgi.com>


* Paul Jackson <pj@sgi.com> wrote:

> I turned on migration_debug=3 at boot, enabled CONFIG_PREEMPT and some 
> other CONFIG DEBUG options, and captured the output from the tty 
> console instead of via the /var/log/messages file.  This resulted in 
> the following.  Now I don't see the BUG, and the cost matrix makes 
> more sense (not all 0's), and the matrix output is not repeated.  I 
> don't understand why.  Feel free to ask me to try various 
> combinations, Ingo, if this doesn't make sense to you either.

hm, these calibration results looks quite sane. Could you try 
migration_debug=3 with the .config that failed before? (if it doesnt 
fail, could you re-check it still fails with migration_debug=2?) Zero 
results in the cost matrix usually are a sign of time resolution 
problems - but that shouldnt be an issue on ia64 which should have a 
globally synced TSC, right?

until these problems are solved, you should be able to work around it by 
booting with the migration_cost=0,7512036,45850376 boot option.

you can work around the warning message via changing the:

	int cpu1 = -1, cpu2 = -1, cpu, orig_cpu = smp_processor_id();

line to:

	int cpu1 = -1, cpu2 = -1, cpu, orig_cpu = raw_smp_processor_id();

i'll do the correct fix.

	Ingo

  reply	other threads:[~2005-11-13  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 21:54 ia64 SN2 - migration costs: 1) nearly zero 2) BUG 3) repeated Paul Jackson
2005-11-12 22:49 ` Paul Jackson
2005-11-13  7:17   ` Ingo Molnar [this message]
2005-11-13 20:13     ` Paul Jackson
2005-11-13 20:23       ` Paul Jackson

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=20051113071716.GA31075@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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