[coreboot] memset called to somewhere high on the stack (uncached)

Myles Watson mylesgw at gmail.com
Fri Apr 9 06:10:38 CEST 2010

On Tue, Apr 6, 2010 at 4:21 PM, Myles Watson <mylesgw at gmail.com> wrote:

> I'm seeing code reads to memset() in coreboot_ram interleaved with byte
> writes to somewhere high on the stack (_estack -0x1fC).  This is a k8.

It turns out init_processor_name() was being called with the cache
disabled.  It doesn't look like it needs to be.  Boot tested on my box.
This makes it more similar to model_10.

Signed-off-by: Myles Watson <mylesgw at gmail.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20100408/507c0bea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uncacheable_mem_writes.diff
Type: text/x-patch
Size: 487 bytes
Desc: not available
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20100408/507c0bea/attachment.diff>

More information about the coreboot mailing list