public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Q] sched: __ARCH_WANT_UNLOCKED_CTXSW on IA64
Date: Wed, 06 Aug 2014 06:27:14 +0000	[thread overview]
Message-ID: <20140806062714.GM9918@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <876351407274890@web12m.yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On Wed, Aug 06, 2014 at 01:41:30AM +0400, Kirill Tkhai wrote:
> Hi, IA64 Gurus,
> 
> I was looking for the reasons of IA64's __ARCH_WANT_UNLOCKED_CTXSW,
> and found the historical commit below:
> 
>     commit f8efa27662532ad5adb2790bfc3f4c78e019cfad
>     Author: Chen, Kenneth W <kenneth.w.chen@intel.com>
>     Date:   Thu Jan 26 18:24:59 2006 -0800
> 
>     [IA64] remove staled comments in asm/system.h
>     
>     With the recent optimization made to wrap_mmu_context function,
>     we don't hold tasklist_lock anymore when wrapping context id.
>     The comments in asm/system.h must fall through the crack earlier.
>     Remove staled comments.
>     
>     I believe it is still beneficial to unlock the runqueue lock
>     across context switch. So leave __ARCH_WANT_UNLOCKED_CTXSW on.
>     
>     Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
>     Signed-off-by: Tony Luck <tony.luck@intel.com>
> 
> The comment confuses a reader. It may seem that the #define
> is not necessary now, no comment around it at all.
> 
> So, could you please point the deadlock we want to avoid
> by __ARCH_WANT_UNLOCKED_CTXSW? I've tried to find, but nothing
> was found by me. No IA64 machines around, so I can't just
> to load kernel w/o this define.

see http://marc.info/?l=linux-kernel&m=131418885605812

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-08-06  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 21:41 [Q] sched: __ARCH_WANT_UNLOCKED_CTXSW on IA64 Kirill Tkhai
2014-08-06  6:27 ` Peter Zijlstra [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=20140806062714.GM9918@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    /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