linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, rutger@nospam.com
Subject: [PATCH] Provide dummy hard_irq_enable/disable() for PPC32
Date: Sun, 26 Nov 2006 17:36:15 +1100	[thread overview]
Message-ID: <20061126063616.A186067B22@ozlabs.org> (raw)

To allow arch/powerpc/kernel/crash.c to build on 32-bit we need a
definition of hard_irq_disable(). 32-bit doesn't support the lazy
interrupt disabling mechanism, so on 32-bit hard_irq_disable() is
simply local_irq_disable(). Add a definition for hard_irq_enable()
just for completeness.

This allows (KEXEC=y && PPC32=y) to build again. Broken since
d04c56f73c30a5e593202ecfcf25ed43d42363a2.

Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
---
Paulus,

if this is OK by you, I think it should probably go in for 2.6.19.

---
 include/asm-powerpc/hw_irq.h |    3 +++
 1 file changed, 3 insertions(+)

Index: powerpc/include/asm-powerpc/hw_irq.h
===================================================================
--- powerpc.orig/include/asm-powerpc/hw_irq.h
+++ powerpc/include/asm-powerpc/hw_irq.h
@@ -92,6 +92,9 @@ static inline void local_irq_save_ptr(un
 #define local_irq_save(flags)	local_irq_save_ptr(&flags)
 #define irqs_disabled()		((mfmsr() & MSR_EE) == 0)
 
+#define hard_irq_enable()	local_irq_enable()
+#define hard_irq_disable()	local_irq_disable()
+
 #endif /* CONFIG_PPC64 */
 
 #define mask_irq(irq)						\

             reply	other threads:[~2006-11-26  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26  6:36 Michael Ellerman [this message]
2006-11-26 18:47 ` [PATCH] Provide dummy hard_irq_enable/disable() for PPC32 Rutger Nijlunsing

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=20061126063616.A186067B22@ozlabs.org \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=rutger@nospam.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).