linux-kernel - Re: [PATCH] x86_64: (NEW) Dynamically allocate arch specific system vectors

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

Date:	Mon, 11 Aug 2008 13:10:16 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Alan Mayer <ajm@....com>, jeremy@...p.org, rusty@...tcorp.com.au,
	suresh.b.siddha@...el.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Dean Nelson <dcn@....com>,
	Cliff Wickman <cpw@....com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <Yinghai.lu@....com>
Subject: Re: [PATCH] x86_64:  (NEW) Dynamically allocate arch specific system vectors

Ingo Molnar <mingo@...e.hu> writes:

> * Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
>> Alan Mayer <ajm@....com> writes:
>> 
>> > Okay, here it is as an attachment.  I think my email client is munging it.
>> > I haven't been able to fix it, apparently.
>> >
>> > I, too, would like to know what Eric thinks.
>> 
>> I think arch/x86 is about to fall over from accidental complexity of 
>> the irq handling. [...]
>
> it was in that state for many years already ;-) Unification, cleanups of 
> other historic messes and the constant push for new hw support just made 
> it stand out more visibly. IRQ and APIC code unification is definitely 
> the final (and by far hardest) major step of x86 unification.

Well I think we are looking at the final couple of straws...

Yes unification (aka porting the infrastructure improvements
to x86_32) and then sharing the code is a piece of it.

>> [...]  Looking at your problem and the problem of killing NR_IRQS I 
>> spent way to much time playing with it this weekend then I should 
>> have, but I think I have found a path that works and is fairly easily 
>> verifiable.
>
> cool :-)
>
>> I have a patch series that gets me 90% of the way there, and the rest 
>> appears easy but I don't have any time to mess with it right now.  I 
>> will try and post it something in the next couple of days.
>
> i'm very interested in it, even if it's incomplete and wont build/boot 
> at all. So please consider posting your existing incomplete series as an 
> RFC right now, maybe we can help finish it sooner than you will find the 
> time? We can put it into a new tip/x86/irq-unification branch, without 
> merging it into tip/master just yet.

Sure. Mostly I just need to allocate a few minutes to post it, later today
or tomorrow hopefully.

Eric


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