From: Ian.Campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH] arm64: remove PSR bit macros from uapi
Date: Mon, 15 Apr 2013 12:48:33 +0100 [thread overview]
Message-ID: <1366026513.4963.106.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <60a204007309b815b1ac115c817dc808@localhost>
On Fri, 2013-04-12 at 17:17 +0100, Marc Zyngier wrote:
> On Fri, 12 Apr 2013 17:06:29 +0100, Ian Campbell <Ian.Campbell@citrix.com>
> wrote:
>
> [...]
>
> > On the flip side is there any reason for the Linux uapi headers to be
> > including architectural constants? e.g. the x86 uapi/ptrace.h doesn't
> > define the RFLAGS bits etc...
>
> My favourite userspace program (aka the other platform emulation that
> shall not ever be merged) needs it. QEMU probably will as well.
>
> Of course, we could define them locally, but that seems like a massive
> waste of perfectly innocent bytes.
I appreciate it's convenient but I'm not sure there is a shortage of
bytes in the world, especially for well known unchanging constants like
this. Your favourite userspace program is a bit of a special case since
it doesn't need to be portable to non-Linux (or I assume not).
Anyway, ignoring the red-herring I introduced the main point isn't that
uapi/ptrace.h includes these definitions (that seems to be OK, standards
wise and is useful to you etc) but rather that they end up infecting
signal.h too. I'll file a bug against glibc/ubuntu/linaro as soon as I
figure out which is the best target...
> or convince the power that be to merge
> the damned thing so we can include kernel headers with any remorse... ;-)
/me steps back several paces and puts away his barge pole. ;-)
Ian.
next prev parent reply other threads:[~2013-04-15 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 15:09 [PATCH] arm64: remove PSR bit macros from uapi Ian Campbell
2013-04-12 15:18 ` Will Deacon
2013-04-12 15:50 ` Ian Campbell
2013-04-12 16:06 ` [Xen-devel] " Ian Campbell
2013-04-12 16:17 ` Marc Zyngier
2013-04-15 11:48 ` Ian Campbell [this message]
2013-04-15 12:28 ` Ian Campbell
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=1366026513.4963.106.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.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