linux-kernel - Re: [PATCH 2/2] x86: Move PCI IO ECS code to x86/pci

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080618075137.GC4135@elte.hu>
Date:	Wed, 18 Jun 2008 09:51:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Robert Richter <robert.richter@....com>
Cc:	Glauber Costa <glommer@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 2/2] x86: Move PCI IO ECS code to x86/pci


* Robert Richter <robert.richter@....com> wrote:

> Ok, so what about shared code? Keep all this in separate files: 
> amd_bus.c, (amd_bus_32.c), amd_bus_64.c, (amd_bus.h)?
> 
> Is the strategy to avoid #ifdefs and instead use the flags in 
> Makefiles? My intention was to coalesce the files. Maybe I was wrong 
> here.

What you did is fine - first step is to move the variants as close to 
each other as possible, in an as obvious and mechanic step as possible.

If anything breaks due to your patches then they were probably too 
large, but lets be optimistic and try your current splitup first :)

Then we can start eliminating any leftover #ifdefs, step by step. Please 
send very, very small patches for that (put them into a git tree on 
kernel.org if there's more than say a dozen of them), we'll test them, 
and if the changes break anything it's all bisectable to an individual 
change.

	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/