public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH] x86: UV cleanup
Date: Thu, 29 Jan 2009 15:30:29 -0600	[thread overview]
Message-ID: <20090129213029.GA29154@sgi.com> (raw)
In-Reply-To: <20090129203517.GE12819@elte.hu>


On Thu, Jan 29, 2009 at 09:35:17PM +0100, Ingo Molnar wrote:
> 
> * Cliff Wickman <cpw@sgi.com> wrote:
> 
> > From: Cliff Wickman <cpw@sgi.com>
> > 
> > This patch tweaks a couple things:
> > 
> > - uv_flush_tlb_others()
> >   the WARN_ON(!in_atomic()); fails if CONFIG_PREEMPT is not enabled
> > 
> >   The #ifdef may not be the right fix. The fix is probably in the
> >   in_atomic macro, but I'm not sure what in_atomic() should return
> >   if CONFIG_PREEMPT is turned off.  I tested making it return 1 in that
> >   case, but that yielded tons of warnings.
> > 
> >   The simpler fix for tlb_uv.c would be to just drop the WARN_ON.
> > 
> > - uv_flush_send_and_wait() should return a pointer if the broadcast
> >   remote tlb shootdown requests fail. That causes the conventional IPI
> >   method of shootdown to be used.
> 
> hm, this isnt a cleanup but a fix - i.e. needs to go into x86/urgent as a 
> separate patch, right?

Yes, it is a fix.  I'll re-post, and send the WARN_ON issue as a
separate patch.

 
> and this:
> 
> > @@ -316,7 +316,9 @@ const struct cpumask *uv_flush_tlb_other
> >  	int locals = 0;
> >  	struct bau_desc *bau_desc;
> >  
> > +#ifdef CONFIG_PREEMPT
> >  	WARN_ON(!in_atomic());
> > +#endif
> 
> is indeed somewhat ugly - and we have no proper primitive to test for 
> atomicity. (mainly because we dont know about atomicity on a non-preempt 
> kernel)
> 
> 	Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824

      reply	other threads:[~2009-01-29 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 19:39 [PATCH] x86: UV cleanup Cliff Wickman
2009-01-29 20:35 ` Ingo Molnar
2009-01-29 21:30   ` Cliff Wickman [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=20090129213029.GA29154@sgi.com \
    --to=cpw@sgi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@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