Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758373AbbBFWYU (ORCPT ); Fri, 6 Feb 2015 17:24:20 -0500 Received: from mga14.intel.com ([192.55.52.115]:39543 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754002AbbBFWYT (ORCPT ); Fri, 6 Feb 2015 17:24:19 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,530,1418112000"; d="scan'208";a="662789840" Message-Id: <7bdbb1a569d487b3a772fbb7b66b9498d6cee551.1423259664.git.tony.luck@intel.com> In-Reply-To: References: From: Tony Luck Date: Tue, 3 Feb 2015 14:40:19 -0800 Subject: [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 752 Lines: 25 Can't post this part yet because it uses things in an upcoming[*] ACPI, UEFI, or some other four-letter-ending-in-I standard. So just imagine a call someplace early in startup that reads information about mirrored address ranges and does: + for (...) { + start = ...; + size = ...; + if (it looks mirrored) + memblock_mark_mirror(start, size); + } Whole patch is pretty tiny: 3 files changed, 19 insertions(+) How much damage could I possibly do in just 19 lines? -Tony [*] very soon, I'm told -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/