public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, paulus@samba.org,
	tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single()
Date: Sat, 22 Mar 2008 13:29:03 +0100	[thread overview]
Message-ID: <20080322122903.GD15355@kernel.dk> (raw)
In-Reply-To: <1FE6DD409037234FAB833C420AA843ECE1387F@orsmsx424.amr.corp.intel.com>

On Fri, Mar 21 2008, Luck, Tony wrote:
> > My thinking was that it may need a bit of help to ensure that the init
> > function for single call data works,
> 
> The problem may be worse than that.  I see that you have a per-cpu
> "call_single_queue" on which you do some list operations.  On ia64
> the per-cpu variables live at the same virtual address on each processor
> with a per-cpu TLB mapping directing them to a different physical
> address on each.  This makes Linux lists very confused.

Funky, how does accessing other CPU's per-cpu variables work on ia64
then? Perhaps I made some false assumptions. Unfortunately I have no
access to any IA64 machines, so I either have to yank the ia64 bits
(which is unfortunate, since Alan tests on those :-) or rely on a bit of
help from you and/or others in getting that bit right.

-- 
Jens Axboe


  reply	other threads:[~2008-03-22 12:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 11:56 [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single() Jens Axboe
2008-03-19 11:56 ` [PATCH 1/5] Add generic helpers for arch IPI function calls Jens Axboe
2008-03-19 11:56 ` [PATCH 2/5] x86: convert to generic helpers for " Jens Axboe
2008-03-19 11:56 ` [PATCH 3/5] x86-64: " Jens Axboe
2008-03-19 11:56 ` [PATCH 4/5] powerpc: " Jens Axboe
2008-03-19 11:56 ` [PATCH 5/5] ia64: " Jens Axboe
2008-03-21  9:53 ` [PATCH 0/5] Generic smp_call_function(), improvements, and smp_call_function_single() Ingo Molnar
2008-03-21 13:15   ` Jens Axboe
2008-03-25  8:00     ` Nick Piggin
2008-03-27 10:08     ` Ingo Molnar
2008-03-27 10:37       ` Jens Axboe
2008-03-27 10:43         ` Ingo Molnar
2008-03-27 12:02           ` Jens Axboe
2008-03-27 12:32             ` Ingo Molnar
2008-03-27 12:35               ` Jens Axboe
2008-03-21 18:22 ` Luck, Tony
2008-03-21 18:31   ` Jens Axboe
2008-03-21 18:56     ` Luck, Tony
2008-03-22 12:29       ` Jens Axboe [this message]
2008-03-24 16:45         ` Luck, Tony
2008-03-24 20:28         ` Luck, Tony
2008-03-25  8:12           ` Jens Axboe
2008-03-25 16:48             ` Luck, Tony
2008-03-25 18:00               ` Jens Axboe
2008-03-21 20:04     ` Luck, Tony

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=20080322122903.GD15355@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=npiggin@suse.de \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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