public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] XPC heartbeat timer function must run on CPU 0
Date: Thu, 15 Nov 2007 17:28:26 +0000	[thread overview]
Message-ID: <20071115172805.GA7095@verge.net.au> (raw)
In-Reply-To: <20071107135306.99AAF11C415@aqua.americas.sgi.com>

On Wed, Nov 14, 2007 at 02:19:15PM -0800, Luck, Tony wrote:
> >> Wouldn't that cpu appear to the new OS instance as cpu0?  If so, then
> >> it should not be an issue.
> >
> > No, I don't believe that it does.
> > I can try and test this theory if it helps.
> > Perhaps my mind is corrupted by x86 thoughts.
> 
> We are talking about logical cpu0 here.  Surely the new instance
> must call whatever cpu it is running on first "0".  E.g. I could
> have used kexec to switch to a UP kernel that only supports cpu0.

I took a look into this, and yes you are right.
Regardless of which physical CPU is used to boot on,
it is always logical cpu 0. So the problem that I
was thinking about doesn't exist. Silly me.

I also noticed that even if it was posisble for logical cpu 0 to
not be present, the patch will still work as the hearbeat
code would just end up being run on the prevailing logical cpu.

So no problem x2 :-)

-- 
Horms, California Edition


      parent reply	other threads:[~2007-11-15 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 13:53 [PATCH] XPC heartbeat timer function must run on CPU 0 Dean Nelson
2007-11-07 16:26 ` Luck, Tony
2007-11-08 12:11 ` Dean Nelson
2007-11-14 20:49 ` Simon Horman
2007-11-14 21:12 ` Robin Holt
2007-11-14 22:11 ` Simon Horman
2007-11-14 22:19 ` Luck, Tony
2007-11-15 17:28 ` Simon Horman [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=20071115172805.GA7095@verge.net.au \
    --to=horms@verge.net.au \
    --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