* Jeremy Fitzhardinge ([EMAIL PROTECTED]) wrote:
Seems to work OK for native and Xen. I had to play a bit with the
paravirt-sched-clock patch to deal with the VMI changes. Zach, can you
check that it still works?
Here's what's working for me on UP. The boot cpu on UP is never getting
the
Dave Jones wrote:
On Wed, Apr 11, 2007 at 10:30:58PM -0700, Zachary Amsden wrote:
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the
heavyweight
xchg instruction to atomically fetch and clear
Zachary Amsden wrote:
In shadow mode hypervisors, ptep_get_and_clear achieves the desired
purpose of keeping the shadows in sync by issuing a native_get_and_clear,
followed by a call to pte_update, which indicates the PTE has been
modified.
Direct mode hypervisors (Xen) have no need for this
From: Paul Mackerras [EMAIL PROTECTED]
Date: Wed, 21 Mar 2007 11:03:14 +1100
Linus Torvalds writes:
We should just do this natively. There's been several tests over the years
saying that it's much more efficient to do sti/cli as a simple store, and
handling the oops, we got an
Zachary Amsden wrote:
Some PTE optimizations for native and paravirt-ops kernels; this
provides a huge win for shadow mode hypervisors and gets rid of
some unnecessary atomic instructions in native kernels, saving
even more on UP by getting rid of implicit LOCK on xchg instruction.
You do
H. Peter Anvin wrote:
Zachary Amsden wrote:
Some PTE optimizations for native and paravirt-ops kernels; this
provides a huge win for shadow mode hypervisors and gets rid of
some unnecessary atomic instructions in native kernels, saving
even more on UP by getting rid of implicit LOCK on xchg
So there is a logic error that would prevent us from ever using NOP
relocations, thus stopping any unnecessary callouts into a VMI ROM. It
doesn't affect us so much, but could conceivably affect open source
implementations of a VMI ROM in the future. It is not absolutely
critical, but it
