Prev: [PATCH 7/7] docbook: use IDs as filenames to support multiple books
Next: bio, fs: update READA and SWRITE to match the corresponding BIO_RW_* bits
From: Andi Kleen on 5 Aug 2010 14:40 Linus, Please pull the hwpoison updates for 2.6.36. This adds basic support for uncorrected memory MCA recovery for huge pages. I have some more stuff (like better handling for slab errors) but it needs a bit more cooking, so currently only Horiguchi-san's code is included. The rmap/hugetlb changes have been reviewed and blessed by the usual suspects. The rmap changes largely use existing infrastructure with just a few tweaks. There is no additional significant overhead for the non error case. -Andi git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-mce-2.6.git hwpoison Naoya Horiguchi (10): hugetlb: move definition of is_vm_hugetlb_page() to hugepage_inline.h hugetlb, rmap: add reverse mapping for hugepage HWPOISON, hugetlb: enable error handling path for hugepage HWPOISON, hugetlb: set/clear PG_hwpoison bits on hugepage HWPOISON, hugetlb: maintain mce_bad_pages in handling hugepage error HWPOISON, hugetlb: isolate corrupted hugepage HWPOISON, hugetlb: detect hwpoison in hugetlb code HWPOISON, hugetlb: support hwpoison injection for hugepage hwpoison: rename CONFIG hugetlb: add missing unlock in avoidcopy path in hugetlb_cow() include/linux/hugetlb.h | 14 +--- include/linux/hugetlb_inline.h | 22 +++++++ include/linux/pagemap.h | 9 +++- include/linux/poison.h | 9 --- include/linux/rmap.h | 5 ++ mm/hugetlb.c | 104 ++++++++++++++++++++++++++++++++++- mm/hwpoison-inject.c | 15 +++-- mm/memory-failure.c | 120 ++++++++++++++++++++++++++++++---------- mm/rmap.c | 59 ++++++++++++++++++++ 9 files changed, 299 insertions(+), 58 deletions(-) create mode 100644 include/linux/hugetlb_inline.h -- ak(a)linux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |