All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] Minutes from LSE Con Call
Date: Fri, 12 Jul 2002 12:40:28 -0700	[thread overview]
Message-ID: <20020712194028.GR25360@holomorphy.com> (raw)
In-Reply-To: <29610000.1026499086@w-hlinder>

On Fri, Jul 12, 2002 at 11:38:06AM -0700, Hanna Linder wrote:
> 8. Daniel asked about seeing results of rmap on a numaq.
> Martin got distracted but will get back to getting some
> results.

On elm3b17 I found more 2.5.25 vs. NUMA-Q issues and got workarounds
for booting while doing work on stuffing pte_chains into highmem:

(1) cpu_init() heisenbug that goes away when adding printk's
	I just added the extra printk's and moved on
(2) in_interrupt() is racy and needs to disable preemption
	while checking per-cpu counters. The trivial fix.
(3) CONFIG_PREEMPT calls preempt_schedule() on secondaries
	before they're ready, and the exception is flagged as
	no vm86_info: BAD
	Didn't want to go to deep into it at 3AM and disabled preempt.

The usual ioremap()/smp_call_function() deadlock, irqbalance
plugging unreachable cpu's into ioapics, bio splitting to make
qlogicisp happy, and MAX_IO_APICS things are still needed.

So I guess the "real fixes" need to get found at some point and
propagated out to maintainers. hpa and mochel are on cpu_init(),
and rml should be on preempt vs. printk and in_interrupt(). axboe
has already got bio splitting ready and no idea about the MAX_IO_APICS
and getting irqbalance fixes past mingo doesn't look easy.


Cheers,
Bill

       reply	other threads:[~2002-07-12 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29610000.1026499086@w-hlinder>
2002-07-12 19:40 ` William Lee Irwin III [this message]
2002-07-12 19:49   ` [Lse-tech] Minutes from LSE Con Call William Lee Irwin III

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=20020712194028.GR25360@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.