From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Cc: d.hatayama@jp.fujitsu.com, kumagai-atsushi@mxc.nes.nec.co.jp,
Baoquan He <bhe@redhat.com>
Subject: [v3 0/3] Introduce struct cycle to store cyclic region and clean up
Date: Sat, 8 Feb 2014 17:19:25 +0800 [thread overview]
Message-ID: <1391851168-6431-1-git-send-email-bhe@redhat.com> (raw)
v1->v2:
In first_cycle(), start_pfn assignation is not aligned to info->pfn_cyclic.
Now in v2 change this. Accordingly the pfn in write_elf_header() and
write_elf_pages_cyclic() need be adjusted to the real beginning of a
load segment, but not the cycle->start_pfn which may be lower after alignment.
v2->v3:
Astushi and HATAYAMA found removing the pfn check in set_bitmap_cyclic will
introduce bugs. So it's better to add the pfn checking back, though there's
a little influence on perforcemance.
Baoquan He (3):
makedumpfile: introduce struct cycle to store the cyclic region
makedumpfile: use struct cycle to update cyclic region and clean up
makedumpfile: remove member variables representing cyclic pfn region
in struct DumpInfo
makedumpfile.c | 498 ++++++++++++++++++++++++++++-----------------------------
makedumpfile.h | 21 +--
sadump_info.c | 4 +-
3 files changed, 261 insertions(+), 262 deletions(-)
--
1.8.3.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2014-02-08 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 9:19 Baoquan He [this message]
2014-02-08 9:19 ` [v3 1/3] makedumpfile: introduce struct cycle to store the cyclic region Baoquan He
2014-02-08 9:19 ` [v3 2/3] makedumpfile: use struct cycle to update cyclic region and clean up Baoquan He
2014-02-08 9:19 ` [v3 3/3] makedumpfile: remove member variables representing cyclic pfn region in struct DumpInfo Baoquan He
2014-02-10 7:58 ` [v3 0/3] Introduce struct cycle to store cyclic region and clean up Atsushi Kumagai
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=1391851168-6431-1-git-send-email-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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