linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 performance counters driver 3.0-pre2 for 2.5.44: [2/4] x86 support
Date: Fri, 25 Oct 2002 14:40:01 +0200	[thread overview]
Message-ID: <20021025124001.GA29937@averell> (raw)
In-Reply-To: <15801.14413.909403.323948@kim.it.uu.se>

> For what values of cpu is per_cpu(var,cpu) valid? For those where
> cpu_online(cpu) is true, or those where cpu_possible(cpu) is true?
> (I need to convert a memset() on the per_cpu_cache[] array to the
> per_cpu(,) framework.)

Currently for cpu_possible(), but there is a patchkit around that
makes it only true for cpu_online() so better assume that. 
Of course that would require a hotplug CPU handler, but I would
just ignore that for now.

-Andi

      reply	other threads:[~2002-10-25 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 15:00 [PATCH] x86 performance counters driver 3.0-pre2 for 2.5.44: [2/4] x86 support Mikael Pettersson
2002-10-24 15:49 ` Andi Kleen
2002-10-25 12:25   ` Mikael Pettersson
2002-10-25 12:40     ` Andi Kleen [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=20021025124001.GA29937@averell \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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;
as well as URLs for NNTP newsgroup(s).