From: David Howells <dhowells@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: [Fwd: [PATCH] Add mm->task_size and fix powerpc vdso]
Date: Tue, 28 Feb 2006 09:22:00 +0000 [thread overview]
Message-ID: <10152.1141118520@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <1141115747.3767.53.camel@localhost.localdomain>
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> Forgot this list on the CC ... Comments welcome, the idea is to finally
> track if an mm is 32 or 64 bits (knowing that I have an urgent need to
> get that fixed in 2.6.16 due to a problem with the powerpc vdso).
Is it possible to end up with a 32-bit and a 64-bit process sharing an
mm_struct? I assume not as I imagine this is set up by execve() which'll
destroy any CLONE_VM sharing.
David
next prev parent reply other threads:[~2006-02-28 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 8:35 [Fwd: [PATCH] Add mm->task_size and fix powerpc vdso] Benjamin Herrenschmidt
2006-02-28 9:22 ` David Howells [this message]
2006-02-28 9:32 ` Benjamin Herrenschmidt
2006-02-28 10:05 ` Paul Mackerras
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=10152.1141118520@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.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