From: Ingo Molnar <mingo@elte.hu>
To: "hpanvin@gmail.com" <hpa@zytor.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL, v2] x86/mm changes for v3.2
Date: Thu, 27 Oct 2011 09:10:54 +0200 [thread overview]
Message-ID: <20111027071054.GA14858@elte.hu> (raw)
In-Reply-To: <6bee402a-c83c-4903-8cf3-24de582247f8@email.android.com>
* hpanvin@gmail.com <hpa@zytor.com> wrote:
> Yes... I thought we had agreed that as ugly as the hook it is
> better than the fragility of second-guessing other code. I would
> like to see something automatically correct by construction, but
> that seems to be really difficult for reasons I don't remember,
> possibly having to do with bad Xen setup APIs.
Okay.
Linus, please ignore this pull request.
Peter, once you get some time please sort out which of these commits
we want to keep:
b17a5f97d413: x86_32: Calculate additional memory needed by the fixmap
2e9fbad5955f: x86-64, mm: Do not assume head_64.S used 4KB pages when !use_pse
1938931a20da: x86, init : Move memblock_x86_reserve_range PGTABLE to find_early_table_space
d8ca7b16cfc1: Revert "x86,xen: introduce x86_init.mapping.pagetable_reserve"
8e7f9f8d4076: x86, mm: Calculate precisely the memory needed by init_memory_mapping
for example 2e9fbad5955f looks independent.
Thanks,
Ingo
next prev parent reply other threads:[~2011-10-27 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 15:36 [GIT PULL] x86/mm changes for v3.2 Ingo Molnar
2011-10-26 16:31 ` Konrad Rzeszutek Wilk
2011-10-26 16:53 ` hpanvin@gmail.com
2011-10-27 7:10 ` Ingo Molnar [this message]
2011-10-27 7:14 ` [GIT PULL, v2] " H. Peter Anvin
2011-10-27 7:14 ` Ingo Molnar
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=20111027071054.GA14858@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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