From: "Mike Frysinger" <vapier.adi@gmail.com>
To: schwidefsky@de.ibm.com
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: CONFIG_HIGHPTE vs. sub-page page tables.
Date: Sat, 9 Feb 2008 12:56:23 -0500 [thread overview]
Message-ID: <8bd0f97a0802090956r2de999fap7f16e173858be240@mail.gmail.com> (raw)
In-Reply-To: <1202554574.8936.15.camel@localhost>
On Feb 9, 2008 5:56 AM, Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> On Sat, 2008-02-09 at 11:37 +0100, Ingo Molnar wrote:
> > i think the worst is over already and i'm reasonably sure that there are
> > no more bugs in it - this _is_ a 1:1 patch after all, so in theory the
> > worst side-effect should be build breakages due to include file
> > spaghetti. The window for this particular breakage was just 256 commits,
> > that's OK i think.
>
> Except for the breakage of all nommu architectures .. they need the
> pgtable_t as well due to the pte_fn_t type.
so why wasnt this in the original patch ? why do no-mmu arches have
to add the pgtable_t typedefs themselves ?
-mike
next prev parent reply other threads:[~2008-02-09 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802081902.m18J2nOm005840@hera.kernel.org>
2008-02-08 23:04 ` Ingo Molnar
2008-02-08 23:15 ` Ingo Molnar
2008-02-09 10:06 ` Martin Schwidefsky
2008-02-09 10:37 ` Ingo Molnar
2008-02-09 10:56 ` Martin Schwidefsky
2008-02-09 17:56 ` Mike Frysinger [this message]
2008-02-10 9:17 ` Martin Schwidefsky
2008-02-10 9:25 ` Mike Frysinger
2008-02-10 9:41 ` Martin Schwidefsky
2008-02-10 10:06 ` Mike Frysinger
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=8bd0f97a0802090956r2de999fap7f16e173858be240@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--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
all inboxes | Powered by JetHome®