On Apr 14, 2008, at 11:44 PM, Paul Mackerras wrote:
Kumar Gala writes:
global_dbcr0 needs to be a per cpu set of save areas instead of a
single
global on all processors.
Looks reasonable. At some point you might want to use a per-cpu
variable instead of an array in order to reduce cacheli
Kumar Gala writes:
> global_dbcr0 needs to be a per cpu set of save areas instead of a single
> global on all processors.
Looks reasonable. At some point you might want to use a per-cpu
variable instead of an array in order to reduce cacheline bouncing.
> Also, we switch to using DBCR0_IDM to d
