Avi Kivity wrote: > We need to distinguish between x86 specific (only x86 has this) and s390 > special (everyone has it except s390). In the latter case it should > still be in common code to avoid duplication, with a guard to disable > compilation on s390. > > KVM_SET_MEMORY_REGION is in theory applicable to non-s390 but I'd like > to deprecate it, so there's no point in implementing it on non-x86. The > rest are s390 special rather than x86 specific. > > As related previously, KVM_SET_USER_MEMORY_REGION should work for s390 > (with an extra check for the guest phsyical start address).
That sounds reasonable to me. I'll make a patch that does this three way split on Monday. Let's see how it comes out. KVM_SET_USER_MEMORY_REGION, and KVM_SET_MEMORY_REGION will go back to common, the irq related ones to a third place. thanks for reviewing, Carsten ------------------------------------------------------------------------- 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
