>> I don't see your concern here. The whole lapic3 is work in > progress, isn't it? Why should we maintain an `old' interface? > Also, as in the second patch, no userspace change is required. >> > > I was thinking about maintenance post 2.6.24. > > However, I'm not opposed to the second patch -- if you think it > worthwhile, it can go in. > OK, we can go in this way since it is still only a IOAPIC/PIC issue which is realtively small in code change. APIC is OK for this since we are definition base on hardware register layout no matter which way.
Let us do this some time later as it doesn't break the ABI. Thx, eddie ------------------------------------------------------------------------- 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
