public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	torvalds@transmeta.com, alan@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: alpha 2.4.13: fix taso osf emulation
Date: Fri, 26 Oct 2001 10:11:45 -0700	[thread overview]
Message-ID: <20011026101145.D1663@redhat.com> (raw)
In-Reply-To: <20011026013101.A1404@redhat.com> <Pine.GSO.3.96.1011026113847.14048A-100000@delta.ds2.pg.gda.pl> <20011026144522.B18880@jurassic.park.msu.ru>
In-Reply-To: <20011026144522.B18880@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Fri, Oct 26, 2001 at 02:45:22PM +0400

On Fri, Oct 26, 2001 at 02:45:22PM +0400, Ivan Kokshaysky wrote:
>  find_vma() only after VM wraparound, which is extremely rare;
>  keeps osf /sbin/loader happy, so no need for alpha-specific routine.

Yes there is, since TASO applications need to wrap at 1<<31, 
not TASK_SIZE.  Note that TASK_SIZE should _not_ be changed
for TASO applications, since they can explicitly map memory
above 4G.  An example here is em86, in which the low 4G is
reserved for the emulated program, and the emulator lives in
high memory.

> Patch appended, comments?

I think you're working too hard to make this "efficient", and
in the process making the code hard to read.  A subroutine
containing a simple search-forward loop is just as effective.


r~

  reply	other threads:[~2001-10-26 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26  8:31 alpha 2.4.13: fix taso osf emulation Richard Henderson
2001-10-26 10:01 ` Maciej W. Rozycki
2001-10-26 10:45   ` Ivan Kokshaysky
2001-10-26 17:11     ` Richard Henderson [this message]
2001-10-29 16:35       ` Ivan Kokshaysky
2001-10-29 17:21         ` Richard Henderson
2001-10-26 17:03   ` Richard Henderson
2001-10-26 18:25     ` Maciej W. Rozycki
2001-10-28  9:38     ` Module loading and Kernel crash Anand Ashok Kulkarni

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=20011026101145.D1663@redhat.com \
    --to=rth@redhat.com \
    --cc=alan@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=torvalds@transmeta.com \
    /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