From: Michael Cree <mcree@orcon.net.nz>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: linux-alpha@vger.kernel.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com
Subject: Re: [PATCH] Alpha: unbreak osf_setsysinfo(SSI_NVPAIRS, [SSIN_UACPROC, UAC_SIGBUS])
Date: Sat, 13 Aug 2011 11:34:58 +1200 [thread overview]
Message-ID: <4E45B8A2.3060806@orcon.net.nz> (raw)
In-Reply-To: <20110813005128.7644d5e4@sf.home>
On 13/08/11 09:51, Sergei Trofimovich wrote:
>> I'll build alpha toolchain / qemu root and will try to cook
>> nicer patch with compile-time safety checks.
>
> Sent reworked patch: http://marc.info/?l=linux-alpha&m=131318270531656&w=2
>
> Yelling at the header I've found minor nit:
> ...
> #define SET_UNALIGN_CTL(task,value) ({ \
> task_thread_info(task)->flags = ((task_thread_info(task)->flags & \
> ~ALPHA_UAC_MASK)
> | (((value) << ALPHA_UAC_SHIFT) & (1<<TIF_UAC_NOPRINT))\
> | (((value) << (ALPHA_UAC_SHIFT + 1)) & (1<<TIF_UAC_SIGBUS)) \
> | (((value) << (ALPHA_UAC_SHIFT - 1)) & (1<<TIF_UAC_NOFIX)));\
> 0; })
>
> #define GET_UNALIGN_CTL(task,value) ({ \
> put_user((task_thread_info(task)->flags & (1 << TIF_UAC_NOPRINT))\
> >> ALPHA_UAC_SHIFT \
> | (task_thread_info(task)->flags & (1 << TIF_UAC_SIGBUS))\
> >> (ALPHA_UAC_SHIFT + 1) \
> | (task_thread_info(task)->flags & (1 << TIF_UAC_NOFIX))\
> >> (ALPHA_UAC_SHIFT - 1), \
> (int __user *)(value)); \
> })
>
> The macros SET_UNALIGN_CTL/GET_UNALIGN_CTL are used
> only in kernel/sys.c:prctl syscall.
>
>> | (((value) << ALPHA_UAC_SHIFT) & (1<<TIF_UAC_NOPRINT))
> prctl.h: # define PR_UNALIGN_NOPRINT 1
>
>> | (((value) << (ALPHA_UAC_SHIFT + 1)) & (1<<TIF_UAC_SIGBUS))
> prctl.h: # define PR_UNALIGN_SIGBUS 2
>
>> | (((value) << (ALPHA_UAC_SHIFT - 1)) & (1<<TIF_UAC_NOFIX)));
>
> prctl.h: no '4' value
>
> Do you think it's worth adding to userspace interface
> or should one just remove it from handled by prctl flags [ABI change]?
My understanding is that user-space ABI changes/removals are
unacceptable. It has been there for some time thus must remain.
But I do note that the NOFIX option is not documented in the prctl
syscall man page or in the prctl application man page, so only someone
acquainted with the kernel code would know it exists.
My feeling is that it should stay the way it is. I'm not aware of a use
for the NOFIX option, and I have no idea why it was originally
implemented -- its implementation predates git history.
But others more familiar with early development of Alpha arch code may
disagree with me.
Cheers
Michael.
prev parent reply other threads:[~2011-08-12 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:25 [PATCH] Alpha: unbreak osf_setsysinfo(SSI_NVPAIRS, [SSIN_UACPROC, UAC_SIGBUS]) slyich
2011-08-12 7:21 ` Michael Cree
2011-08-12 9:59 ` Sergei Trofimovich
2011-08-12 21:51 ` Sergei Trofimovich
2011-08-12 23:34 ` Michael Cree [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=4E45B8A2.3060806@orcon.net.nz \
--to=mcree@orcon.net.nz \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--cc=slyich@gmail.com \
/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