Messages in this thread | | | Date | Tue, 31 Aug 2004 21:51:07 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] voluntary-preempt-2.6.9-rc1-bk4-Q5 |
| |
* Lee Revell <rlrevell@joe-job.com> wrote:
> Commented out all calls to wbinvd(), seems to work fine. I even tried > repeatedly killing the X server before it could finish starting, no > problems at all. > > I guess the worst that could happen here would be display corruption, > which would get fixed on the next refresh?
it's more complex than that - MTRR's are caching attributes that the CPU listens to. Mis-setting them can cause anything from memory corruption to hard lockups. The question is, does any of the Intel (or AMD) docs say that the CPU cache has to be write-back flushed when setting MTRRs, or were those calls only done out of paranoia?
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |