On Tue, Nov 13, 2007 at 02:09:41PM +0100, Andi Kleen wrote: > >> If vsmp is selected, PARAVIRT will be too, and the interrupt code will >> be patched. >> the vsmp option triggers a select statement. >> >> the ifdef only exists because, as I said, the code itself will be always >> compiled in, to avoid an ifdef in setup_64.c. So it's just a taking it >> from here, putting it there issue. > >Peeking around needlessly in pci config space at each boot just to avoid an >ifdef is not an good idea.
Agreed. vsmp_init does not make sense unless the irq ops are patched. We can call vsmp_init under #ifdef CONFIG_PARAVIRT. Thanks, Kiran ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
