[Xen-devel] [PATCH] Mini-os get_current() fixup

Hi,

I'm currently playing with mini-os, and noticed bogus code:

0x00019301 <do_page_fault+81>:  mov    $0x1,%ecx
0x00019306 <do_page_fault+86>:  mov    $0xffffe000,%eax
0x0001930b <do_page_fault+91>:  mov    %ecx,0x32980
0x00019311 <do_page_fault+97>:  and    %esp,%edx
0x00019313 <do_page_fault+99>:  mov    (%edx),%ecx
0x00019315 <do_page_fault+101>: mov    (%ecx),%eax

Which is supposed to approximately correspond to get_current(). It
happens that %edx is never set to 0xfffff000. The attached patch fixes
that.

Samuel

patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] Mini-os get_current() fixup, Samuel Thibault <= Re: [Xen-devel] [PATCH] Mini-os get_current() fixup, Samuel Thibault Message not available [Xen-devel] Re: [PATCH] Mini-os xenbus wait fixup, Samuel Thibault

Previous by Date:

Re: [Xen-devel] [VTD][PATCH] Don't allow assigning the same device twice without release the first assignment, Keir Fraser

Next by Date:

Re: [Xen-devel] [PATCH] Mini-os get_current() fixup, Samuel Thibault

Previous by Thread:

[Xen-devel] [VTD][PATCH] Don't allow assigning the same device twice without release the first assignment, Han, Weidong

Next by Thread:

Re: [Xen-devel] [PATCH] Mini-os get_current() fixup, Samuel Thibault

Indexes:

[Date] [Thread] [Top] [All Lists]