From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Pavel Machek <pavel@denx.de>
Cc: Phil Turmel <philip@turmel.org>, "H. Peter Anvin" <hpa@zytor.com>,
paul.szabo@sydney.edu.au, ben@decadent.org.uk,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PAE problems was [RFC] Reproducible OOM with just a few sleeps
Date: Wed, 06 Feb 2013 16:28:08 -0800 [thread overview]
Message-ID: <5112F518.3020003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130201102545.GA3053@amd.pavel.ucw.cz>
On 02/01/2013 02:25 AM, Pavel Machek wrote:
> Ouch, and... IIRC (hpa should know for sure), PAE is neccessary for
> R^X support on x86, thus getting more common, not less. If it does not
> work, that's bad news.
Dare I ask what "R^X" is?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Pavel Machek <pavel@denx.de>
Cc: Phil Turmel <philip@turmel.org>, "H. Peter Anvin" <hpa@zytor.com>,
paul.szabo@sydney.edu.au, ben@decadent.org.uk,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PAE problems was [RFC] Reproducible OOM with just a few sleeps
Date: Wed, 06 Feb 2013 16:28:08 -0800 [thread overview]
Message-ID: <5112F518.3020003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130201102545.GA3053@amd.pavel.ucw.cz>
On 02/01/2013 02:25 AM, Pavel Machek wrote:
> Ouch, and... IIRC (hpa should know for sure), PAE is neccessary for
> R^X support on x86, thus getting more common, not less. If it does not
> work, that's bad news.
Dare I ask what "R^X" is?
next prev parent reply other threads:[~2013-02-07 0:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 3:31 [RFC] Reproducible OOM with just a few sleeps paul.szabo
2013-01-12 3:31 ` paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36 ` paul.szabo
2013-01-14 20:36 ` paul.szabo
2013-01-15 0:34 ` Bug#695182: " Ben Hutchings
2013-01-15 0:56 ` Dave Hansen
2013-01-15 0:56 ` Dave Hansen
2013-01-15 2:16 ` paul.szabo
2013-01-15 2:16 ` paul.szabo
2013-01-30 12:51 ` Pavel Machek
2013-01-30 12:51 ` Pavel Machek
2013-01-30 15:32 ` Dave Hansen
2013-01-30 15:32 ` Dave Hansen
2013-01-30 19:40 ` paul.szabo
2013-01-30 19:40 ` paul.szabo
2013-01-31 5:15 ` Bug#695182: " Ben Hutchings
2013-01-31 9:07 ` paul.szabo
2013-01-31 9:07 ` paul.szabo
2013-01-31 13:38 ` Ben Hutchings
2013-01-31 23:06 ` paul.szabo
2013-01-31 23:06 ` paul.szabo
2013-02-01 1:07 ` Ben Hutchings
2013-02-01 2:12 ` paul.szabo
2013-02-01 2:12 ` paul.szabo
2013-02-01 2:57 ` Ben Hutchings
2013-02-01 3:13 ` paul.szabo
2013-02-01 3:13 ` paul.szabo
2013-02-01 4:38 ` Phil Turmel
2013-02-01 4:38 ` Phil Turmel
2013-02-01 10:20 ` Pavel Machek
2013-02-01 10:20 ` Pavel Machek
2013-02-01 10:25 ` PAE problems was " Pavel Machek
2013-02-01 10:25 ` Pavel Machek
2013-02-01 16:57 ` H. Peter Anvin
2013-02-01 16:57 ` H. Peter Anvin
2013-02-01 17:45 ` Ben Hutchings
2013-02-07 0:28 ` Dave Hansen [this message]
2013-02-07 0:28 ` Dave Hansen
2013-02-10 19:09 ` Pavel Machek
2013-02-10 19:09 ` Pavel Machek
2013-02-17 9:10 ` Simon Jeons
2013-02-17 9:10 ` Simon Jeons
2013-02-24 22:10 ` paul.szabo
2013-02-24 22:10 ` paul.szabo
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=5112F518.3020003@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=ben@decadent.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
--cc=pavel@denx.de \
--cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.