Zachary Amsden wrote:
> Ok. As long as we plan on patching CR2 and CR0 / clts accessors for
> FPU save during context switch and page fault paths in the future.
That's up to each backend, right? Or do these need to be patched for a
correctness reason?
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Zachary Amsden <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- From: Zachary Amsden <[email protected]>
- Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Prev by Date: Re: [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot
- Next by Date: Serial driver doesn't handle FIFO error ?
- Previous by thread: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Next by thread: Re: [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions
- Index(es):
 |