Messages in this thread | | | Date | Mon, 17 Mar 2014 12:19:31 +0000 | Subject | Re: [Xen-devel] [PATCHv1] x86: don't schedule when handling #NM exception | From | George Dunlap <> |
| |
On Mon, Mar 17, 2014 at 3:33 AM, H. Peter Anvin <hpa@zytor.com> wrote: > No, the right thing is to unf*ck the Xen braindamage and use eagerfpu as a workaround for the legacy hypervisor versions.
The interface wasn't an accident. In the most common case you'll want to clear the bit anyway. In PV mode clearing it would require an extra trip up into the hypervisor. So this saves one trip up into the hypervisor on every context switch which involves an FPU, at the expense of not being able to context-switch away when handling the trap.
-George
| |