From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch] ia64: fix potential NaT bit error for sys_pipe().
Date: Fri, 21 Jan 2005 03:32:48 +0000 [thread overview]
Message-ID: <200501210332.j0L3Wmg24796@unix-os.sc.intel.com> (raw)
In-Reply-To: <16878.2168.388519.26567@napali.hpl.hp.com>
>>>>> On Thu, 20 Jan 2005 15:22:59 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
>
> Rohit> We are also thinking of reseting the mfh bit on every syscall
> Rohit> entry as an optimization.
>
> Rohit> Comments?
David Mosberger wrote on Thursday, January 20, 2005 3:51 PM
> Sounds OK with me. We should delete this comment from process.c then,
> ....
> and change:
>
> #define THREAD_FLAGS_TO_CLEAR (IA64_THREAD_FPH_VALID | IA64_THREAD_DBG_VALID \
> | IA64_THREAD_PM_VALID)
>
> to:
>
> #define THREAD_FLAGS_TO_CLEAR (IA64_THREAD_DBG_VALID | IA64_THREAD_PM_VALID)
We would rather not to change THREAD_FLAGS_TO_CLEAR definition. mfh bit in child
pt_regs is cleared right above where the comment is. I think it is better as is
so that child thread fph partition stays invalidated.
- Ken
next prev parent reply other threads:[~2005-01-21 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 7:12 [patch] ia64: fix potential NaT bit error for sys_pipe() David Mosberger
2005-01-20 17:52 ` David Mosberger
2005-01-20 19:00 ` Seth, Rohit
2005-01-20 23:22 ` Seth, Rohit
2005-01-20 23:51 ` David Mosberger
2005-01-21 3:32 ` Chen, Kenneth W [this message]
2005-01-21 18:48 ` Chen, Kenneth W
2005-01-24 6:40 ` David Mosberger
2005-01-24 19:17 ` David Mosberger
2005-01-24 19:32 ` Chen, Kenneth W
2005-01-24 19:43 ` 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=200501210332.j0L3Wmg24796@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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