On Fri, 19 Oct 2012 11:17:53 -0400 Vivek Goyal <vgoyal at redhat.com> wrote: [..] > On Fri, Oct 19, 2012 at 12:20:54PM +0900, HATAYAMA Daisuke wrote: > I am skeptical that this approach is going to fly in practice. Dumping > huge images, processing and transferring these is not very practical. > So I would rather narrow down the problem on a running system and take > filtered dump of appropriate component where I suspect the problem is. > > [..] > > > capability was the primary reason that s390 also wants to support > > > kdump otherwise there firmware dumping mechanism was working just > > > fine. > > > > > > > I don't know s390 firmware dumping mechanism at all, but is it > > possble for s390 to filter crash dump even on firmware dumping > > mechanism? > > AFAIK, s390 dump mechanism could not filter dump and tha's the reason > they wanted to support kdump and /proc/vmcore so that makedumpfile > could filter it. I am CCing Michael Holzheu, who did the s390 kdump > work. He can tell it better. Correct. The other s390 dump mechanisms (stand-alone and hypervisor dump) are not able to do filtering and therefore the handling of large dumps has been a problem for us. This was one of the main reasons to implement kdump on s390. Michael
