linux-kernel - Re: [PATCH] X86: Change the default value of nr_irqs from 32 to NR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <48ACA75A.9070306@goop.org>
Date:	Wed, 20 Aug 2008 16:23:06 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"Alex Nixon (Intern)" <Alex.Nixon@...rix.com>
CC:	Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] X86: Change the default value of nr_irqs from 32 to NR_IRQs

Alex Nixon (Intern) wrote:
> I'm not sure about the general case, but Xen does not (Jeremy correct
> me if I'm wrong).
>

No, no apics of any kind in the PV domU case.

> Unless I'm missing something (which I may well be; I'm new to this
> area of code), it seems more logical anyway to default back to the
> calculated system-specific value (NR_IRQS), instead of 32, which seems
> rather arbitrary.
>

I think the patch looks fine for now.  But now that we seem to have
unified the use of vectors (I haven't looked at the current code closely
yet), I'd like to move Xen to mapping event channels -> vectors rather
than IRQs, and have the per-cpu event channels share an irq.  That will
dramatically decrease the irq requirements for a PV domU (to 6 irqs +
devices, rather than 6/cpu + devices; a typical domain may only need 10
irqs overall).

    J

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/