Richard Henderson writes: > On 08/26/2013 09:59 AM, Paolo Bonzini wrote: >>> I don't understand the point of this. There is one alpha emulation; >>> if you disable it you're left with a program that's not useful. So >>> why the configuration for it at all? >> >> I think this was just for consistency with other targets. Either this >> patch can be left out completely, or the symbol can be made default on >> and unchangeable by the user.
> Yeah, maybe. I'll be interested to see the v2 cover-letter with your > requested > description of what the series brings to the table. Didn't look much into the patches, so I'm not sure if this includes both the configuration and build system for Linux, but the kernel's build system might provide a more robust and flexible build system. > This isn't the kernel, where non-pagable code size is a concern, so I don't > see > how full configuration of machine emulations and devices is helpful. I'd be > more inclined to go the other way, where all qemu-system-cpu images always > build in all devices (compiled once of course). Which reminds me of some older discussion about having a single QEMU binary able to emulate a system with CPUs from different architectures (with a future^2 version of qom'ified CPUs). Such fine-grained compilation would deviate even more from that goal (assuming it's a goal). Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth
