From: Jay Lan <jlan@sgi.com>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: Neil Horman <nhorman@redhat.com>,
kexec@lists.infradead.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] makedumpfile: Shrink the time for creating 1st-bitmap (Re: problems in kdump kernel if 'maxcpus=1' not specified?)
Date: Thu, 17 Jul 2008 10:09:04 -0700 [thread overview]
Message-ID: <487F7CB0.7040902@sgi.com> (raw)
In-Reply-To: <487EE836.7010607@mxs.nes.nec.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
Ken'ichi Ohmichi wrote:
> Hi Jay,
>
> Ken'ichi Ohmichi wrote:
>> I created the attached patch that makedumpfile does not scan
>> memory gap when creating 1st-bitmap. Could you please try it ?
>> This patch is for makedumpfile-1.2.6.
>
> I found a bug in the patch I sent before, and I fixed it in the
> attached patch. Could you please try this patch ?
> Sorry for my mistake.
Hi Ken'ichi San,
Thanks for your patch. I need to compete for the test machine. Will
post new data when i have one.
Regards,
- jay
>
>
> Thanks
> Ken'ichi Ohmichi
>
> diff -puN backup/v1.2.6/makedumpfile.c makedumpfile/makedumpfile.c
> --- backup/v1.2.6/makedumpfile.c 2008-06-05 15:17:17.000000000 +0900
> +++ makedumpfile/makedumpfile.c 2008-07-18 00:14:34.000000000 +0900
> @@ -3987,8 +3987,10 @@ exclude_free_page()
> int
> create_1st_bitmap()
> {
> + int i;
> char *buf = NULL;
> - unsigned long long pfn, paddr;
> + unsigned long long pfn, pfn_start, pfn_end, pfn_bitmap1;
> + struct pt_load_segment *pls;
> off_t offset_page;
> int ret = FALSE;
>
> @@ -4021,13 +4023,19 @@ create_1st_bitmap()
> /*
> * If page is on memory hole, set bit on the 1st-bitmap.
> */
> - for (pfn = 0, paddr = 0; pfn < info->max_mapnr;
> - pfn++, paddr += info->page_size) {
> - if (is_in_segs(paddr))
> + for (i = pfn_bitmap1 = 0; i < info->num_load_memory; i++) {
> + pls = &info->pt_load_segments[i];
> + pfn_start = pls->phys_start >> PAGESHIFT();
> + pfn_end = pls->phys_end >> PAGESHIFT();
> + if (!is_in_segs(pfn_start << PAGESHIFT()))
> + pfn_start++;
> + for (pfn = pfn_start; pfn < pfn_end; pfn++) {
> set_bit_on_1st_bitmap(pfn);
> - else
> - pfn_memhole++;
> + pfn_bitmap1++;
> + }
> }
> + pfn_memhole = info->max_mapnr - pfn_bitmap1;
> +
> if (!sync_1st_bitmap())
> goto out;
>
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-17 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 1:07 problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:12 ` Vivek Goyal
2008-07-16 15:25 ` Neil Horman
2008-07-16 16:23 ` Vivek Goyal
2008-07-16 17:03 ` Neil Horman
2008-07-16 19:16 ` Jay Lan
2008-07-17 4:59 ` Ken'ichi Ohmichi
2008-07-17 6:35 ` [PATCH] makedumpfile: Shrink the time for creating 1st-bitmap (Re: problems in kdump kernel if 'maxcpus=1' not specified?) Ken'ichi Ohmichi
2008-07-17 17:09 ` Jay Lan [this message]
2008-07-18 4:00 ` Ken'ichi Ohmichi
2008-07-18 15:57 ` Jay Lan
2008-07-16 18:00 ` problems in kdump kernel if 'maxcpus=1' not specified? Jay Lan
2008-07-16 15:26 ` Bernhard Walle
2008-07-16 16:34 ` Vivek Goyal
2008-07-16 16:45 ` Bernhard Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487F7CB0.7040902@sgi.com \
--to=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox