On Thu, Nov 21, 2013 at 11:57:46PM +0000, Jim MacArthur wrote: > On 21 November 2013 07:27, Gleb Natapov <gleb@xxxxxxxxxx> wrote: > > On Thu, Nov 21, 2013 at 12:39:49AM +0000, Jim MacArthur wrote: > >> After reading this I added a call to KVM_GET_SREGS. Everything you say > >> here matches my experience except that CS.base=0xf0000. > >> So I adjusted my memory to cover physical address 0xFFFF0, and now > >> it's happily running instructions (NOPs, at least.) > >> I'm a bit puzzled that it didn't start with CS.base=0xffff0000, but it > >> doesn't matter, I've done what I wanted to do for now. > >> > > What is your kernel version? > > This is on a Mac mini: Linux version 3.2.0-56-generic > (buildd@roseapple) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) > #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 > > I get the same results from 3.2.0-4-amd64 on my thinkpad. > > The code I'm running is at http://pastebin.com/Z1SR5Vid. > > It's likely to be because I'm doing something wrong, and I've got what > I wanted working anyway. Thanks again for your help. No, this is because old kernels started in incorrect state, on recent kernels KVM_GET_SREGS will return correct one. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
