From: "Paweł Sikora" <pluto@agmk.net>
To: linux-kernel@vger.kernel.org
Subject: Re: proxy_pda was Re: What was in the x86 merge for .20
Date: Mon, 15 Jan 2007 21:41:02 +0100 [thread overview]
Message-ID: <200701152141.02403.pluto@agmk.net> (raw)
Hi,
I've reviewed the thread and can propose a solution.
Let's see e.g. the dev.s ( from fuse.ko ). Currently with gcc-4.2 we get:
fuse_req_init_context:
movl $_proxy_pda+8, %edx #, tmp62
#APP
movl %gs:8,%ecx #, ret__
#NO_APP
movl 344(%ecx), %ecx # <variable>.fsuid, <variable>.fsuid
movl %ecx, 60(%eax) # <variable>.fsuid, <variable>.in.h.uid
#APP
movl %gs:8,%ecx #, ret__
#NO_APP
movl 360(%ecx), %ecx # <variable>.fsgid, <variable>.fsgid
movl %ecx, 64(%eax) # <variable>.fsgid, <variable>.in.h.gid
#APP
movl %gs:8,%edx #, ret__
#NO_APP
movl 164(%edx), %edx # <variable>.pid, <variable>.pid
movl %edx, 68(%eax) # <variable>.pid, <variable>.in.h.pid
ret
In this scenario gcc is explictly blocked by -fno-strict-aliasing
and massive %gs:8 reloads are present. If you fix aliasing violations
in kernel then you could use -fstrict-aliasing to get what you want.
fuse_req_init_context:
#APP
movl %gs:8,%ecx #, ret__
#NO_APP
movl 344(%ecx), %edx # <variable>.fsuid, <variable>.fsuid
movl %edx, 60(%eax) # <variable>.fsuid, <variable>.in.h.uid
movl 360(%ecx), %edx # <variable>.fsgid, <variable>.fsgid
movl %edx, 64(%eax) # <variable>.fsgid, <variable>.in.h.gid
movl 164(%ecx), %edx # <variable>.pid, <variable>.pid
movl %edx, 68(%eax) # <variable>.pid, <variable>.in.h.pid
ret
BR,
Pawel.
next reply other threads:[~2007-01-15 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 20:41 Paweł Sikora [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-08 3:01 What was in the x86 merge for .20 Andi Kleen
2006-12-08 12:04 ` Arkadiusz Miskiewicz
2006-12-08 20:35 ` Jeremy Fitzhardinge
2006-12-08 21:06 ` proxy_pda was " Andi Kleen
2006-12-08 21:09 ` Jeremy Fitzhardinge
2006-12-08 21:22 ` Andi Kleen
2006-12-08 21:34 ` Jeremy Fitzhardinge
2006-12-08 22:04 ` Arkadiusz Miskiewicz
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=200701152141.02403.pluto@agmk.net \
--to=pluto@agmk.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.