The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Sebastian Reichel <sre@kernel.org>
Cc: Kai Vehmanen <kvehmanen@nosignal.fi>,
	Aaro Koskinen <aaro.koskinen@iki.fi>, Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH] HSI: cmt_speech: fix timestamp interface
Date: Fri, 10 Apr 2015 22:11:43 +0200	[thread overview]
Message-ID: <2731231.Ic3nBHVb1n@wuerfel> (raw)
In-Reply-To: <20150410133609.GA8029@earth>

On Friday 10 April 2015 15:36:10 Sebastian Reichel wrote:
> 
> > - The layout is incompatible between 32-bit and 64-bit user
> >   space, because of the size differences in 'struct timespec'.
> >   This means that the driver can not work when used with 32-bit
> >   user space on a 64-bit kernel.
> > 
> > - As there are plans to change 32-bit user space to use
> >   a 64-bit time_t type in the future, it will also be
> >   incompatible with new 32-bit user space.
> > 
> > As the driver is not yet widely used, now would be a good time
> > to change it to just use a 64-bit nanosecond value, which also
> > happens to be more efficient. In order to make the layout
> > non-ambiguous, we have to also add extra padding so the 64-bit
> > value is naturally aligned.
> > 
> > The change requires the respective update to user space tools
> > using it. If that is for some reason not possible any more,
> > another solution would be to replace the timespec structure
> > with two __u32 values to avoid incompatibilities later.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> 
> I think updating to two __u32 values is the better solution here.
> While the driver is new in the mainline kernel it has been used
> for multiple years downstream in the Maemo/MeeGo/Mer communities
> and I would prefer to keep userspace compatibility.

Ok. You still need to update that userspace to the new ABI in order
to support compiling on 64-bit machines and on future arm32 with
64-bit time_t, but existing binaries will continue to run.

Can you (or someone on Cc) prepare a patch for this?

	Arnd

  reply	other threads:[~2015-04-10 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 11:59 [RFC, PATCH] HSI: cmt_speech: fix timestamp interface Arnd Bergmann
2015-04-10 13:36 ` Sebastian Reichel
2015-04-10 20:11   ` Arnd Bergmann [this message]
2015-04-16 17:13     ` [PATCH] " Sebastian Reichel
2015-04-23 13:37       ` Thomas Gleixner
2015-05-04 14:04         ` Sebastian Reichel
2015-05-04 14:02       ` Sebastian Reichel

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=2731231.Ic3nBHVb1n@wuerfel \
    --to=arnd@arndb.de \
    --cc=aaro.koskinen@iki.fi \
    --cc=kvehmanen@nosignal.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sre@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