From: Ingo Molnar <mingo@elte.hu>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: ak@suse.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, markus.t.metzger@gmail.com,
suresh.b.siddha@intel.com, roland@redhat.com,
akpm@linux-foundation.org, mtk.manpages@gmail.com,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [patch 1/2] x86, ptrace: add version and last remaining size to status command
Date: Tue, 8 Jan 2008 10:50:30 +0100 [thread overview]
Message-ID: <20080108095030.GI27671@elte.hu> (raw)
In-Reply-To: <20080107133346.A11643@sedona.ch.intel.com>
* Markus Metzger <markus.t.metzger@intel.com> wrote:
> Return the API version and the size of a bts_struct in the
> PTRACE_BTS_STATUS command. This might be handy in case other archs
> want to use and extend the interface. It allows users to program
> against one version and continue to work for newer versions (they have
> to discard everything they don't understand, of course).
i think this will be quite handy. But:
+ /* actual size of bts_struct in bytes */
+ unsigned short bts_size;
+ /* interface version */
+ unsigned short version;
please dont use shorts. Lets just us bts_size and no version at all, ok?
Any change to the ABI will be extension and that can be done by changing
the size of the data structure. We try to avoid doing versioned APIs in
Linux syscalls.
and while at it, how about using u32/u64 for the fields (that's how we
expose ABIs, even if we know that 'unsigned int' is always 32-bit on
x86), and add support for COMPAT as well?
Ingo
next prev parent reply other threads:[~2008-01-08 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 12:33 Markus Metzger
2008-01-08 9:50 ` Ingo Molnar [this message]
2008-01-08 10:17 ` [patch 1/2] x86, ptrace: add version and last remaining sizeto " Metzger, Markus T
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=20080108095030.GI27671@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mtk.manpages@gmail.com \
--cc=roland@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®