From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Nathan Lynch <nathanl@austin.ibm.com>
Subject: Re: pSeries_mach_cpu_die() question
Date: Fri, 02 Jun 2006 16:26:26 +1000 [thread overview]
Message-ID: <1149229586.16202.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20060602061929.GM8934@localdomain>
On Fri, 2006-06-02 at 01:19 -0500, Nathan Lynch wrote:
> The cpu parameter is actually unused by in the lpar case:
Ok, missed that :)
> > - xics has a xics_teardown_cpu() now, used by kexec, that does
> > something very similar except that it passes the proper CPU number, and
> > for secondary CPUs also does an EOI of any pending IPI (just in case). I
> > think that could be used instead of the direct call to the low level
> > pSeriesLP_* funciton (which I itend to unexport and rename anyway as
> > part of my rework). Can whoever knows that code confirm ?
>
> Sounds okay to me.
Ok. I'll call it with 0 for the "secondary" argument so it doesn't do
the additional EOI of the IPI in order to not change behaviour from the
current code. We can do differently in the future if we want.
> The comment should be changed or removed really. We got away without
> doing plpar_cppr() on the Power4 hypervisor but we found out it was
> necessary when testing Power5. I think it's required by the
> architecture regardless, and yes, it's safe on both platforms.
I'll remove the comment.
Thanks !
Cheers,
Ben.
prev parent reply other threads:[~2006-06-02 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 5:16 pSeries_mach_cpu_die() question Benjamin Herrenschmidt
2006-06-02 6:19 ` Nathan Lynch
2006-06-02 6:26 ` 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=1149229586.16202.57.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nathanl@austin.ibm.com \
--cc=ntl@pobox.com \
/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).