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 02:35:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005073@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005061@msgid-missing>
>>>>> On Wed, 17 Jan 2001 13:12:41 -0500 (EST), William Taber <wtaber@rational.com> said:
William> When I downloaded Linux 2.4.0 and applied the
William> linux-2.4.0-ia64-010109.diff patch, I discovered that I could no
William> longer compile ia32 kernels. It turned out that there were
William> reletively few changes needed to get the ia32 kernel to compile
William> cleanly and come up and run. As I promised yesterday, here are the
William> patches I needed to make. This may not be exhaustive, since I do not
William> have all options turned on and I didn't try to build many
William> drivers. Note that this patch will remove the buggy code that I
William> reported yesterday, rather than just conditionalizing it. Since the
William> code was broken and would not run properly, as well as being
William> non-portable, I just took it out pending a fix. In the interest of
William> getting the latest ia64 changes ready for merging into the the main
William> 2.4.x tree at some point, here are the diffs.
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
next prev parent reply other threads:[~2001-01-18 2:35 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 [this message]
2001-01-18 15:47 ` William Taber
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-105590693005073@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