From: William Taber <wtaber@rational.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PATCH: Building on ia32
Date: Thu, 18 Jan 2001 15:47:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005075@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005061@msgid-missing>
>
>But your patch breaks the lazy-execute bit scheme that IA-64 relies on to avoid
>cache flushing. Your kernel will probably hang on any app that does dynamic
>code generation (e.g., such as due to nested C functions).
>
>You're probably better off implementing is_exec_access() on x86 as always
>returning 0.
>
> --david
David,
Actually, I think the best solution is to move is_exec_access() and
is_write_access() out of asm-ia64/pgtable.h, and into some machine independent
header (perhaps mm.h ?), redefining the magic numbers 2 and 4 to be VM_WRITE
and VM_EXEC respectively. This still leaves the question of who is
responsible for changing all of the platform specific callers of
handle_mm_fault to reflect the new semantics?
Will
+---------------------------------------------------------------------+
| Will Taber |
| Software Engineer, CMBU E-mail wtaber@rational.com |
| Rational Software Corporation Phone: 781-676-2436 |
| 20 Maguire Road, Lexington, Mass. 02421 |
+---------------------------------------------------------------------+
next prev parent reply other threads:[~2001-01-18 15:47 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 [this message]
2001-01-18 16:29 ` David Mosberger
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-105590693005075@msgid-missing \
--to=wtaber@rational.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