Thanks for the reply. I guess we have pretty much nailed down device bringup sequence when loading under capture kernel. Our concern is: the capture kernel has a significant smaller memory footprint. Our RAID driver itself has a large memory requirement, some of which could fail allocation when loaded under the capture kernel.
If we could somehow determine that we are being called in context of capture kernel, we can dynamically lower driver memory requirement (at cost of lower IO throughout of-course, which is ok for this brief context). Thanks -Atul -----Original Message----- From: Vivek Goyal [mailto:[EMAIL PROTECTED] Sent: Tue 9/18/2007 9:53 PM To: Mukker, Atul Cc: [EMAIL PROTECTED]; Kexec Mailing List Subject: Re: kdump info request On Tue, Sep 18, 2007 at 03:13:42PM -0600, Mukker, Atul wrote: > Hello Vivek, Hari: > > > > Excuse me for contacting you direct, but seems like you 2 can point me > to a right direction for a kdump question we have. > > > > We are trying to make sure our RAID driver works ok when kernel is > loaded with kdump. Is there a way for driver to detect this condition; > that is, current kernel is running with kdump. We need this information > so we can scale down certain operations in the driver. > Hi Atul, What do you mean by detecting if current kernel is running with kdump? Do you mean that you want to know the moment somebody loads a capture kernel by kexec -p and driver will change some of its behaviour? I think that's not the right way to go about. Explain the issue a little bit in detail. Generally drivers run into issues while initializing in second kernel and one of the way to handle it is reset the device before going further with initialization. I am hoping your RAID controller provides some kind of reset mechanism from software. Thanks Vivek
_______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
