public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>,
	Namhyung Kim <namhyung.kim@lge.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code: asm/8267
Date: Wed, 27 Mar 2013 17:38:06 +0100	[thread overview]
Message-ID: <20130327163806.GC8385@pd.tnic> (raw)
In-Reply-To: <20130327163427.GN30540@8bytes.org>

On Wed, Mar 27, 2013 at 05:34:27PM +0100, Joerg Roedel wrote:
> Interesting read, thanks guys. I think I should have a look into the
> tree-preempt implementation and try to understand it :)

Hurry, before paulmck comes and changes it unrecognizable! :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-03-27 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 11:55 BUG: using smp_processor_id() in preemptible [00000000] code: asm/8267 Borislav Petkov
2013-03-24 15:59 ` Borislav Petkov
2013-03-26 18:34   ` Borislav Petkov
2013-03-27  6:02     ` Namhyung Kim
2013-03-27  9:49       ` Borislav Petkov
2013-03-27 10:42         ` Jiri Olsa
2013-03-27 14:09         ` Peter Zijlstra
2013-03-27 16:31           ` Borislav Petkov
2013-04-30 15:27           ` [RFCv2] " Jiri Olsa
2013-03-27 13:15     ` Joerg Roedel
2013-03-27 14:17       ` Peter Zijlstra
2013-03-27 14:37         ` Paul E. McKenney
2013-03-27 16:34           ` Joerg Roedel
2013-03-27 16:38             ` Borislav Petkov [this message]
2013-03-27 18:04               ` Paul E. McKenney
2013-03-27 19:07                 ` Borislav Petkov
2013-03-27 19:20                   ` Borislav Petkov
2013-03-27 19:22                   ` Paul E. McKenney

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=20130327163806.GC8385@pd.tnic \
    --to=bp@alien8.de \
    --cc=acme@infradead.org \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.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