On Fri, 2006-04-14 at 12:00 -0500, Dave Jones wrote: [snip] > arch/i386/kernel/cpu/intel.c has a bunch of workarounds for various > issues. Is there a valid use-case for ever booting with cache disabled > though? If so, this should probably be a boot-time option to enable it. Yes, disabling the cache is useful to debug bad hardware. If the CPU cache is bad, then disabling it might make things work again and you know what needs to be replaced. -- Zan Lynx <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Where to call L2 cache enabling code from?
- From: Steve Snyder <[email protected]>
- Re: Where to call L2 cache enabling code from?
- From: Alan Cox <[email protected]>
- Re: Where to call L2 cache enabling code from?
- From: Steve Snyder <[email protected]>
- Re: Where to call L2 cache enabling code from?
- From: Dave Jones <[email protected]>
- Where to call L2 cache enabling code from?
- Prev by Date: Re: [PATCH rc1-mm 2/3] coredump: shutdown current process first
- Next by Date: Re: [i386, x86-64] ioapic_register_intr() and assign_irq_vector() questions
- Previous by thread: Re: Where to call L2 cache enabling code from?
- Next by thread: [PATCH] make: add modules_update target
- Index(es):
 |