From: ebiederm@xmission.com (Eric W. Biederman)
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, ink@jurassic.park.msu.ru,
linux-kernel@vger.kernel.org, rth@twiddle.net, davej@redhat.com,
zwane@arm.linux.org.uk, ak@suse.de, ashok.raj@intel.com
Subject: Re: [PATCH] alpha build pm_power_off hack
Date: Mon, 12 Dec 2005 05:10:34 -0700 [thread overview]
Message-ID: <m1u0dea539.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051211222404.d35f990c.pj@sgi.com> (Paul Jackson's message of "Sun, 11 Dec 2005 22:24:04 -0800")
Paul Jackson <pj@sgi.com> writes:
> Eric wrote:
>> Taking a quick glance at alpha causes me to think we always
>> want pm_power_off to be non null on alpha.
>
> So I presume you think that some alpha person should write
> such a function?
Sorry I had about 5 minutes to do something when this issue
came up and unfortunately I knew how to solve it cleanly :(
So I wrote the patch. It was my hope that by putting it into
-mm I could sucker someone with some time into doing fixing
the architectures that broke.
I think what we want is one of the too patches below. Basically
something that just sets pm_power_off to a non NULL value is
enough to continue the alphas current behaviour.
> I can't quite guess whether you are agreeing with my patch,
> or disagreeing with it.
Disagreeing in saying it didn't quite go far enough pm_power_off
should be initialized on alpha.
> At the very least, I don't want to leave the crosstools build
> of alpha with a default config broken.
That is a good point. But I really don't want to see a fix that
just blindly fixes a build issue. When it takes about 10 minutes
to audit machine_power_off and see what really needs to be done.
To that extent I have hacked up your patch two different ways
one of them should be usable. I'm just not certain which non-zero
initializer I like better. The second setting pm_power_off to
machine_power_off is what the powerpc port currently does.
Eric
---
arch/alpha/kernel/process.c | 5 +++++
1 files changed, 5 insertions(+)
--- 2.6.15-rc5-mm2.orig/arch/alpha/kernel/process.c 2005-12-11
15:07:52.000000000 -0800
+++ 2.6.15-rc5-mm2/arch/alpha/kernel/process.c 2005-12-11 15:09:33.000000000
-0800
@@ -43,6 +43,11 @@
#include "proto.h"
#include "pci_impl.h"
+/*
+ * Power off function, alpha doesn't use but we should
+ * always call machine_power_off.
+ */
+void (*pm_power_off)(void) = ERR_PTR(-EINVAL);
+
void
cpu_idle(void)
{
---
arch/alpha/kernel/process.c | 5 +++++
1 files changed, 5 insertions(+)
--- 2.6.15-rc5-mm2.orig/arch/alpha/kernel/process.c 2005-12-11
15:07:52.000000000 -0800
+++ 2.6.15-rc5-mm2/arch/alpha/kernel/process.c 2005-12-11 15:09:33.000000000
-0800
@@ -43,6 +43,11 @@
#include "proto.h"
#include "pci_impl.h"
+/*
+ * Power off function, alpha doesn't use but we should
+ * always call machine_power_off.
+ */
+void (*pm_power_off)(void) = machine_power_off;
+
void
cpu_idle(void)
{
next prev parent reply other threads:[~2005-12-12 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 23:24 Paul Jackson
2005-12-12 5:23 ` Eric W. Biederman
2005-12-12 6:24 ` Paul Jackson
2005-12-12 12:10 ` Eric W. Biederman [this message]
2005-12-12 13:44 ` Ivan Kokshaysky
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=m1u0dea539.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=davej@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rth@twiddle.net \
--cc=zwane@arm.linux.org.uk \
/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
Powered by JetHome