Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752173AbbEFX3T (ORCPT ); Wed, 6 May 2015 19:29:19 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:56439 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751666AbbEFX3R (ORCPT ); Wed, 6 May 2015 19:29:17 -0400 Date: Wed, 6 May 2015 16:29:16 -0700 From: Andrew Morton To: Tony Luck Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 0/3] Find mirrored memory, use for boot time allocations Message-Id: <20150506162916.d19f9d82cecd0d96897d7835@linux-foundation.org> In-Reply-To: References: X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 16 On Mon, 4 May 2015 13:52:23 -0700 Tony Luck wrote: > UEFI published the spec that descibes the attribute bit we need to > find out which memory ranges are mirrored. So time to post the real > version of this series. Can we please have an explanation for why we're doing this? Reading further I see that the intent is to put kernel data structures into mirrored memory. Why is this a good thing? -- 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/