On Fri, 2006-06-16 at 11:00 +0900, Isaku Yamahata wrote:
On Thu, Jun 15, 2006 at 01:14:06PM -0600, Al Stone wrote:
In all of the functions above, it appears that the return value of
a function (pte_offset_map()) is being returned as a volatile result
from each of the functions. Is that
On Thu, 2006-06-15 at 11:58 +0900, Isaku Yamahata wrote:
2 / 7
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID 03b29286001dea87284cc401492a799e7e654a0f
# Parent ad418fdb1981be2108d84bafbd294a9db9899396
add volatile pte entry of the p2m table.
Since p2m table are shared
On Thu, Jun 15, 2006 at 01:14:06PM -0600, Al Stone wrote:
In all of the functions above, it appears that the return value of
a function (pte_offset_map()) is being returned as a volatile result
from each of the functions. Is that really needed? I'm not sure
it helps in this case, but I
2 / 7
# HG changeset patch
# User [EMAIL PROTECTED]
# Node ID 03b29286001dea87284cc401492a799e7e654a0f
# Parent ad418fdb1981be2108d84bafbd294a9db9899396
add volatile pte entry of the p2m table.
Since p2m table are shared by cpu. volatile is needed.
fix the races in pte access of
