linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Mitesh R. Meswani" <mmeswani@miners.utep.edu>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Finding cpuid in entry_64.S
Date: Tue, 19 Aug 2008 11:59:07 +1000	[thread overview]
Message-ID: <1219111147.8062.6.camel@pasglop> (raw)
In-Reply-To: <BLU103-DS41DBE50328F80B52EA442936E0@phx.gbl>

On Mon, 2008-08-18 at 17:33 -0600, Mitesh R. Meswani wrote:
> Hello 
>  
> I am trying to find the cpuid when the functions that handle return
> from context switch and interrupts are called, based on the cpu the
> return code is executing on, I want to take some specific actions. 

What are you trying to do more precisely ? It sounds like the wrong
solution to whatever problem you have ... 

Ben.

      reply	other threads:[~2008-08-19  1:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 23:33 Finding cpuid in entry_64.S Mitesh R. Meswani
2008-08-19  1:59 ` Benjamin Herrenschmidt [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=1219111147.8062.6.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mmeswani@miners.utep.edu \
    /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).