Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757351Ab3GOX4a (ORCPT ); Mon, 15 Jul 2013 19:56:30 -0400 Received: from mail-we0-f177.google.com ([74.125.82.177]:37842 "EHLO mail-we0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753834Ab3GOX43 (ORCPT ); Mon, 15 Jul 2013 19:56:29 -0400 MIME-Version: 1.0 In-Reply-To: <20130715230418.GA2649@leaf> References: <20130715230418.GA2649@leaf> Date: Mon, 15 Jul 2013 19:56:27 -0400 Message-ID: Subject: Re: BGRT Pointer in System RAM From: Parag Warudkar To: Josh Triplett Cc: Andy Lutomirski , LKML , linux-acpi@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 609 Lines: 15 On Mon, Jul 15, 2013 at 7:04 PM, Josh Triplett wrote: > We do need to handle the case of a valid pointer into memory that e820 > calls system RAM, as well as the case of a valid pointer into memory > reserved for the BIOS or similar, but not the case of an invalid > pointer. Would that be as simple as page_is_ram( -- 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/