Avi Kivity wrote: > I don't think we should aim for keeping control registers in an arch > independent manner, since there is nothing common among the different > architectures in that area. For x86, keeping them in an array is not > helpful since the individual control registers have nothing to do with > each other. Also, for most things like the fpu and segment registers > this trick won't work. > > I suggest keeping them in an arch dependent structure (struct > kvm_vcpu_arch) in <asm/kvm.h>. We can then access them through a member > as vcpu->arch.cr0, etc. Fine with me, I gonna patch that direction.
------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
