From: Matt Chapman <matthewc@hp.com>
To: linux-ia64@vger.kernel.org
Subject: __copy_user exception handling
Date: Fri, 29 Jul 2005 22:10:44 +0000 [thread overview]
Message-ID: <20050729221044.GA23144@kirby.fc.hp.com> (raw)
The main __copy_user loop looks like this:
2:
EX(.failure_in3,(p16) ld8 val1[0]=[src1],16)
(p16) ld8 val2[0]=[src2],16
EX(.failure_out, (EPI) st8 [dst1]=val1[PIPE_DEPTH-1],16)
(EPI) st8 [dst2]=val2[PIPE_DEPTH-1],16
br.ctop.dptk 2b
What I'm trying to understand is why there is no EX necessary on the
second store. As far as I understand the implementation, src is 16-byte
aligned here, so there is no need for EX on the second load, since it
necessarily hits the same page. But dst is only 8-byte aligned, so I
would think that the second store could fault.
I've done some testing and for some reason it doesn't seem to be a
problem in Linux; I haven't been able to produce an oops. But I've hit
oopses in Xen (we use the same code), and so I'm trying to understand
*why* it's not a problem in Linux.
Does anyone have some insight?
Matt
next reply other threads:[~2005-07-29 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 22:10 Matt Chapman [this message]
2005-07-29 23:23 ` __copy_user exception handling Chen, Kenneth W
2005-07-29 23:33 ` Matt Chapman
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=20050729221044.GA23144@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