linux-kernel - Re: [PATCH 0/5 resend] x86, ioapic: Clean up ioapic idx and apic id usage

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20111012094711.GA21090@elte.hu>
Date:	Wed, 12 Oct 2011 11:47:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai.lu@...cle.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Naga Chumbalkar <nagananda.chumbalkar@...com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5 resend] x86, ioapic: Clean up ioapic idx and apic id
 usage



* Yinghai Lu <yinghai.lu@...cle.com> wrote:

> Resending x86/ioapic clean up patches.
> 
> it will make sure ioapic_idx is used instead of ioapic or apic_idx to used as index.
> 
> [PATCH 1/5] x86, ioapic: Passing irq_attr struct pointer with setup_ioapic_irq()
> [PATCH 2/5] x86, ioapic: Split setup_ioapic_entry for interrupt remapped version
> [PATCH 3/5] x86, ioapic: Print out irte with right ioapic index
> [PATCH 4/5] x86, ioapic: Seperate print_IO_APIC() to only print one io apic
> [PATCH 5/5] x86, ioapic: Clean up ioapic/apic_id usage
> 
> patch1, 2, 4, 5 are cleanup related
> patch3 fixes the one idx printout.

Applied to tip:x86/apic, thanks!

Another io_apic.c issue that Thomas raised is that we should 
standardize arch/x86 on SPARSE_IRQ=y and get rid of all
SPARSE_IRQ=n complications.

Thanks,

	Ingo
--
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/