From: Sinan Nalkaya <sardok@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Sinan Nalkaya <sardok@gmail.com>
Subject: [uml-devel] [PATCH 1/1] um: Fix broken IRQs if SPARSE_IRQ is selected
Date: Thu, 7 Feb 2013 01:39:00 +0200 [thread overview]
Message-ID: <1360193940-31504-1-git-send-email-sardok@gmail.com> (raw)
um: Kconfig.common: enabled SPARSE_IRQ.
um: kernel/irq: arch_probe_nr_irqs is implemented to prevent use of the default.
Signed-off-by: Sinan Nalkaya <sardok@gmail.com>
---
arch/um/Kconfig.common | 1 +
arch/um/kernel/irq.c | 7 +++++++
2 files changed, 8 insertions(+)
diff --git a/arch/um/Kconfig.common b/arch/um/Kconfig.common
index 648121b..8335fdd 100644
--- a/arch/um/Kconfig.common
+++ b/arch/um/Kconfig.common
@@ -12,6 +12,7 @@ config UML
select GENERIC_CPU_DEVICES
select GENERIC_IO
select GENERIC_CLOCKEVENTS
+ select SPARSE_IRQ
config MMU
bool
diff --git a/arch/um/kernel/irq.c b/arch/um/kernel/irq.c
index 36e12f0..93615f0 100644
--- a/arch/um/kernel/irq.c
+++ b/arch/um/kernel/irq.c
@@ -356,6 +356,13 @@ void __init init_IRQ(void)
irq_set_chip_and_handler(i, &normal_irq_type, handle_edge_irq);
}
+#ifdef CONFIG_SPARSE_IRQ
+int __init arch_probe_nr_irqs(void)
+{
+ return NR_IRQS;
+}
+#endif
+
/*
* IRQ stack entry and exit:
*
--
1.7.10.4
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2013-02-06 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1360193940-31504-1-git-send-email-sardok@gmail.com \
--to=sardok@gmail.com \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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