The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: mathieu.desnoyers@polymtl.ca, linux-kernel@vger.kernel.org,
	macro@ds2.pg.gda.pl
Subject: Re: [PATCH][2.4.23-pre3] repair mpparse for default MP systems
Date: Thu, 11 Sep 2003 23:16:19 -0400	[thread overview]
Message-ID: <20030912031619.GA1310@Krystal> (raw)
In-Reply-To: <16224.62817.533540.928220@gargle.gargle.HOWL>

* Mikael Pettersson (mikpe@csd.uu.se) wrote:
> Mathieu,
> 
> This patch for 2.4.23-pre3 should fix the problems your dual
> P5 with default MP config has been having since 2.4.21-pre2.
> Please let us know if it works or not.
> 
> /Mikael
> 

Yes, I just tested this patch, and everything seems to work fine. Thank
you. :)

The only point I see, which is not triggered on my machine (because of
the absence of ACPI) is this one :

There is also an initialization of this mp_irqs variable in
mp_config_acpi_legacy_irqs from mpparse.c. It only seems to be called
from within acpi_boot_init in acpi.c. So I wonder if it's possible that
we do use default configuration and then also go into
mp_config_acpi_legacy_irqs during the acpi init, thus reserving the
memory twice and forgetting the old pointer, which could lead to an
erratic result.

If it's possible, then there is still a problem in there.

OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

  reply	other threads:[~2003-09-12  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 22:21 [PATCH][2.4.23-pre3] repair mpparse for default MP systems Mikael Pettersson
2003-09-12  3:16 ` Mathieu Desnoyers [this message]
2003-09-12  9:31   ` Mikael Pettersson
2003-09-12 11:58     ` Maciej W. Rozycki

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=20030912031619.GA1310@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=mikpe@csd.uu.se \
    /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