Thanks for your advice. :) It have nothing to do with smp, though each domain shares one apic_access_page now. In fact, currently this page won't be accessed, just a address mark for cpu.
Avi Kivity wrote: > Yang, Sheng wrote: >> Hi Avi, >> >> I've been work on other things for long time, so this patch delayed for >> a while. I am planning to post it out recently, but found that, because >> of userspace allocate memory patch, rmap was moved to memslot. So your >> suggestion on deal it with gfn_to_page seems got a little trouble. And I >> don't perfer to use one memslot to do this kind of thing alone. >> > > I think that adding a memory slot is a good first step. Later if it > shows up in profiles we can replace it with something else, but right > now let's keep things simple. > > It should probably be an internal memory slot, so we don't need to > change userspace to use this feature, and we can react to changes in the > apic base address. > > (An internal memory slot would also be useful for storing the real-mode > tss on Intel) > > Question: how does this interact with SMP? Does each vcpu require its > own page? Thanks Yang, Sheng ------------------------------------------------------------------------- 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
