Re: [tip:x86/cpu] x86, cpu: AMD errata checking framework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/08/2010 07:18 AM, Hans Rosenfeld wrote:
> 
> Thats exactly the kind of thing I wanted to avoid. This means carrying
> around all errata definitions in memory all the time instead of just
> when theres actually code thats using them.
> 

On a note on that... by passing the definition as arguments you're doing
it asas *code*, which is seriously bloated over a memory structure.  The
size of memory structures should be insignificant, and would be cold in
memory anyway.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux