public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PATCH:  Building on ia32
Date: Thu, 18 Jan 2001 16:29:27 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005076@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005061@msgid-missing>

>>>>> On Thu, 18 Jan 2001 10:47:07 -0500 (EST), William Taber <wtaber@rational.com> said:

  William> Actually, I think the best solution is to move
  William> is_exec_access() and is_write_access() out of
  William> asm-ia64/pgtable.h, and into some machine independent
  William> header (perhaps mm.h ?), redefining the magic numbers 2 and
  William> 4 to be VM_WRITE and VM_EXEC respectively.  This still
  William> leaves the question of who is responsible for changing all
  William> of the platform specific callers of handle_mm_fault to
  William> reflect the new semantics?

The sole reason for the existence of those macros is so they can be
defined in a platform-specific way.  No other platform is currently
using lazy-execute bits and on those platforms, there is no need to
check the executable bit in the page fault handler.  However, I don't
think is_exec_access() is the final answer either---that's why I don't
bother updating the other ports: it's still very much works in
progress.

	--david


      parent reply	other threads:[~2001-01-18 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 18:12 [Linux-ia64] PATCH: Building on ia32 William Taber
2001-01-18  2:35 ` David Mosberger
2001-01-18 15:47 ` William Taber
2001-01-18 16:29 ` David Mosberger [this message]

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=marc-linux-ia64-105590693005076@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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