From: Tom Rini <trini@ti.com>
To: Jacob Shin <jacob.shin@amd.com>
Cc: X86-ML <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped
Date: Sun, 21 Oct 2012 14:22:43 -0700 [thread overview]
Message-ID: <20121021212243.GA2867@bill-the-cat> (raw)
In-Reply-To: <1345852516-3125-3-git-send-email-jacob.shin@amd.com>
On Fri, Aug 24, 2012 at 06:55:13PM -0500, Jacob Shin wrote:
> Current logic finds enough space for direct mapping page tables from 0
> to end. Instead, we only need to find enough space to cover mr[0].start
> to mr[nr_range].end -- the range that is actually being mapped by
> init_memory_mapping()
>
> This patch also reportedly fixes suspend/resume issue reported in:
>
> https://lkml.org/lkml/2012/8/11/83
>
> Signed-off-by: Jacob Shin <jacob.shin@amd.com>
This fixes a bug I see that was introduced in 1bbbbe7
Tested-by: Tom Rini <trini@ti.com>
--
Tom
next prev parent reply other threads:[~2012-10-21 21:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 23:55 [PATCH V4 0/5] x86: Create direct mappings for E820_RAM only Jacob Shin
2012-08-24 23:55 ` [PATCH 1/5] x86: Move enabling of PSE and PGE out of init_memory_mapping Jacob Shin
2012-08-25 1:25 ` Yinghai Lu
2012-08-25 1:49 ` Yinghai Lu
2012-08-25 2:06 ` Yinghai Lu
2012-08-25 4:15 ` Jacob Shin
2012-08-25 4:13 ` Jacob Shin
2012-08-24 23:55 ` [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped Jacob Shin
2012-10-21 21:22 ` Tom Rini [this message]
2012-08-24 23:55 ` [PATCH 3/5] x86: Only direct map addresses that are marked as E820_RAM Jacob Shin
2012-08-25 0:17 ` Jacob Shin
2012-08-25 0:30 ` H. Peter Anvin
2012-08-25 0:49 ` Jacob Shin
2012-08-25 1:13 ` H. Peter Anvin
2012-08-25 4:20 ` Jacob Shin
2012-08-25 4:21 ` H. Peter Anvin
2012-08-27 19:17 ` Jacob Shin
2012-08-27 20:15 ` H. Peter Anvin
2012-08-25 1:07 ` Yinghai Lu
2012-08-25 4:24 ` Jacob Shin
2012-08-25 4:54 ` Yinghai Lu
2012-08-27 18:49 ` Jacob Shin
2012-08-27 20:16 ` H. Peter Anvin
2012-08-28 16:06 ` Jacob Shin
2012-08-28 16:11 ` H. Peter Anvin
2012-08-24 23:55 ` [PATCH 4/5] x86: Fixup code testing if a pfn is direct mapped Jacob Shin
2012-08-24 23:55 ` [PATCH 5/5] x86: if kernel .text .data .bss are not marked as E820_RAM, complain and fix Jacob Shin
2012-08-25 1:23 ` Yinghai Lu
2012-08-25 4:25 ` Jacob Shin
-- strict thread matches above, loose matches on Subject: below --
2012-08-13 21:46 [PATCH V2 0/5] x86: Create direct mappings for E820_RAM only Jacob Shin
2012-08-13 21:47 ` [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped Jacob Shin
2012-08-09 21:23 [PATCH 0/5] Only create direct mappings for E820_RAM regions Jacob Shin
2012-08-09 21:23 ` [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped Jacob Shin
2012-08-11 19:56 ` Tejun Heo
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=20121021212243.GA2867@bill-the-cat \
--to=trini@ti.com \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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