On Mon, Jan 26, 2015 at 01:11:42PM +0100, Joerg Roedel wrote:
> Well, there is no easy way. But we could collect information from the
> loaded drivers on boot about how many dma-memory they allocate and base
> our allocation on that.
That sounds like a nifty idea to me.
> Or we solve it in user-space by some more cleverness in creating the
> kernel command-line for crashkernel=high.
I'd say, we should try to do as much as possible automatically.
> But besides that, I think the first two patches of this set make sense
> anyway. I understand that the third one is debatable.
Right, but since they fix a real problem, maybe we should take them now
until a better fix is done? Yes, no?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
