Messages in this thread | | | Date | Wed, 28 Jul 2010 09:06:03 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [PATCH 31/31] memblock: Add memblock_find_in_range() |
| |
On 07/28/2010 12:12 AM, Yinghai Lu wrote: > > the problem is later if the user hit the problem, it will be called "Regression" after bisecting to the memblock/x86 changes. > because low/high does work before. > > BTW, that design from qlogic to save log in RAM is not good one, they may save some cents for the ram in card. > > other vendors seems put log/trace in the ram on card. >
It's broken NOW. The only reason it's not exploding is by accident. The fact that you knew about the problem and had the notion of working around it instead of fixing the root cause by either fixing or blacklisting the broken driver is disgusting beyond belief.
Either the driver needs to map the memory off limit in the e820 map passed to kexec, or better yet it should have its DMA disabled across kexec. I'm truly appalled.
-hpa
-- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
| |