From: Matt Chapman <matthewc@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: __copy_user exception handling
Date: Fri, 29 Jul 2005 23:33:58 +0000 [thread overview]
Message-ID: <20050729233358.GA32341@kirby.fc.hp.com> (raw)
In-Reply-To: <20050729221044.GA23144@kirby.fc.hp.com>
On Fri, Jul 29, 2005 at 04:23:33PM -0700, Chen, Kenneth W wrote:
>
> Because exception handler use to work at instruction bundle granularity.
> The first EX would automatically catch the 2nd ld8 or st8, with a caveat
> that this code is assuming gcc 2.x tool chain. With moving to gcc 3.x
> assembler where it understand local tag support, the exception handler
> works at instruction granularity and then all the sudden, it falls flat
> on its face.
Ah right.
> Are you sure you want to use this code? It's for first incarnation of
> Itanium. The kernel has an optimized version of copy_user for Itanium2.
> See memcpy_mck.S
Aha, thank you! That explains why I can't trigger that bug in Linux
on Itanium 2. I'll make Xen use the memcpy_mck.S version.
Matt
prev parent reply other threads:[~2005-07-29 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 22:10 __copy_user exception handling Matt Chapman
2005-07-29 23:23 ` Chen, Kenneth W
2005-07-29 23:33 ` Matt Chapman [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=20050729233358.GA32341@kirby.fc.hp.com \
--to=matthewc@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