Randy Dunlap <[email protected]> writes:
> I don't know if this patch is trying to solve this (->) problem, but there
> is a desire for drivers to have a decent way to tell if the kernel that
> is executing is a kexec/crash kernel or not. If it is a kexec/crash
> kernel, then (some) drivers may not allocate as many buffers as they
> normally do, since the kernel would likely be configured to use
> less memory. The solution doesn't have to involve sysfs .. or it could.
The patch is trying to make it easier to observe new fields passed to
the kernel by the bootloader in user space.
The drivers should have a way to look at the amount of memory the
kernel is configured to use and operate on that. I expect this is a
general embedded scenario.
I don't think I have seen a driver concern in the kdump environment
that is unique to that environment. So in general I figure we should
use whatever it is that is different about the kdump environment that
the causes the drivers to want to do something differently, so the
changes can ideally support more people.
Eric
--
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
