From: Prarit Bhargava <prarit@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -v2] x86, irq: get correct available vectors for cpu disable
Date: Tue, 28 Jan 2014 13:43:10 -0500 [thread overview]
Message-ID: <52E7FA3E.4000400@redhat.com> (raw)
In-Reply-To: <1390769416-2835-1-git-send-email-yinghai@kernel.org>
On 01/26/2014 03:50 PM, Yinghai Lu wrote:
> assign_irq_vector will stop before first_system_vector.
> also it will not vector that is set in used_vectors.
>
> used_vectors is used to track non per_cpu irq_vector in vector_irq.
> It include first 32 exception [0,1f) and system vector near 0xfe.
> and IA32_SYSCALL_VECTOR (0x80), IRQ_MOVE_CLEANUP_VECTOR (0x20).
>
> So add checking for them for counting avaiable vectors.
>
Yinghai, no objection to the patch ... but how about
used_vectors is a bitmap for global irqs; it tracks the non per_cpu
irq_vectors in vector_irq. used_vectors contains information on the first 32
exceptions (0 to 0x1f), the system vectors near the first system vector
(0xfe), the IA32_SYSCALL_VECTOR (0x80), and the IRQ_MOVE_CLEANUP_VECTOR (0x20)
assign_irq_vectors() assigns vectors up to first_system_vector (0xfe) and
sets the used_vectors bit for each assigned vector. Currently, the
IRQ checking code only scans from the FIRST_EXTERNAL_VECTOR to the end of
the vectors. This patch modifies the code to scan to first_system_vector
and do a test on the used_vectors bitmap.
... and ...
> -v2: fix compiling problem.
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> ---
> arch/x86/kernel/irq.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> Index: linux-2.6/arch/x86/kernel/irq.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/irq.c
> +++ linux-2.6/arch/x86/kernel/irq.c
> @@ -17,6 +17,7 @@
> #include <asm/idle.h>
> #include <asm/mce.h>
> #include <asm/hw_irq.h>
> +#include <asm/desc.h>
>
> #define CREATE_TRACE_POINTS
> #include <asm/trace/irq_vectors.h>
> @@ -321,8 +322,19 @@ int check_irq_vectors_for_cpu_disable(vo
> for_each_online_cpu(cpu) {
> if (cpu == this_cpu)
> continue;
> - for (vector = FIRST_EXTERNAL_VECTOR; vector < NR_VECTORS;
> - vector++) {
> +
> + /*
> + * assign_irq_vector() only use vector under
> + * first_system_vector and not set in used_vectors bitmask.
> + * used_vectors could have bits set for
> + * IA32_SYSCALL_VECTOR (0x80)
> + * IRQ_MOVE_CLEANUP_VECTOR (0x20)
> + */
+ /*
+ * assign_irq_vector() will only scan non per_cpu vectors from
+ * FIRST_EXTERNAL_VECTOR to first_system_vector (0xfe) and not
+ * set in used_vectors bitmask. This takes into account
+ * the IA32_SYSCALL_VECTOR and the IRQ_MOVE_CLEANUP_VECTOR,
+ * which should not be counted.
+ */
... what do you think?
P.
> + for (vector = FIRST_EXTERNAL_VECTOR;
> + vector < first_system_vector; vector++) {
> + if (test_bit(vector, used_vectors))
> + continue;
> +
> if (per_cpu(vector_irq, cpu)[vector] < 0)
> count++;
> }
next prev parent reply other threads:[~2014-01-28 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 20:50 Yinghai Lu
2014-01-28 18:43 ` Prarit Bhargava [this message]
2014-01-28 21:47 ` Yinghai Lu
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=52E7FA3E.4000400@redhat.com \
--to=prarit@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome