On Friday 02 September 2005 00:17, Jeff Dike wrote:
> From: Bodo Stroesser <[EMAIL PROTECTED]>
>
> Add new cmdline setups:
> - noprocmm
> - noptracefaultinfo
> In case of testing, they can be used to switch off usage of
> /proc/mm and PTRACE_FAULTINFO independently.
Is "skas0" cmd line option p
On Iau, 2005-09-01 at 18:16 -0400, Jeff Dike wrote:
> This fixes a build breakage introduced by Alan's tty cleanups. This should
> be tied to that patch if possible.
>
> Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
>
> Index: linux-2.6.13-mm1/arch/um/drivers/chan_kern.c
> ===
On Wed, Aug 31, 2005 at 07:06:33PM -0400, Allan Graves wrote:
> Jeff,
> Here's the patches. Hope these meet your approval!
> Allan
Some comments - I have these all fixed:
+struct task_struct *from=(struct task_struct*)prev;
+struct task_struct *to=(struct task_str
On Fri, Sep 02, 2005 at 12:39:23PM +0200, Blaisorblade wrote:
> Is "skas0" cmd line option preserved?
Yes, it is.
Jeff
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005
On Fri, 26 Aug 2005, Blaisorblade wrote:
>
> * The first 2 patches modify the PTE encoding macros and start preparing the
> VM for the new situation (i.e. VMA which have variable protections, which are
> called VM_NONUNIFORM. I dropped the early VM_MANYPROTS name).
What a pity: please revert.
On Wed, Aug 10, 2005 at 09:37:28PM +0200, Blaisorblade wrote:
> Also look, on the "set_pte" theme, at the attached patch.
+ WARN_ON(!pte_young(*pte) || pte_write(*pte) && !pte_dirty(*pte));
This one has been firing on me, and I decided to figure out why. The
culprit is this code in do_no_
On Fri, 2 Sep 2005, Jeff Dike wrote:
> On Wed, Aug 10, 2005 at 09:37:28PM +0200, Blaisorblade wrote:
> > Also look, on the "set_pte" theme, at the attached patch.
>
> + WARN_ON(!pte_young(*pte) || pte_write(*pte) && !pte_dirty(*pte));
>
> This one has been firing on me, and I decided to fi