linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: "André Hentschel" <nerv@dawncrow.de>
Cc: Matthieu CASTET <matthieu.castet@parrot.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm: Preserve TPIDRURW on context switch
Date: Thu, 21 Feb 2013 10:33:43 +0000	[thread overview]
Message-ID: <20130221103342.GA20566@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <5125254D.7040401@dawncrow.de>

Hi Andre,

On Wed, Feb 20, 2013 at 07:34:37PM +0000, André Hentschel wrote:
> Am 12.02.2013 16:02, schrieb Matthieu CASTET:
> > The tls value is never saved to : thread->tp_value[1].
> > 
> > Also I don't know if you can avoid the extra ldr in the software case.
>
> seems like Matthieu is right, any update on this?

Yeah, I'll get round to this after the merge window and send a v2.
I have a nice long flight to Hong Kong on the horizon, which may well drive
me to writing patches :)

Cheers,

Will

      reply	other threads:[~2013-02-21 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 22:43 [PATCH] arm: Preserve TPIDRURW on context switch André Hentschel
2013-02-06 22:51 ` Russell King - ARM Linux
2013-02-06 23:01   ` André Hentschel
2013-02-08 15:48     ` Will Deacon
2013-02-09 16:44       ` André Hentschel
2013-02-12 14:02       ` André Hentschel
2013-02-12 14:09         ` Will Deacon
2013-02-12 14:14           ` André Hentschel
2013-02-12 15:02           ` Matthieu CASTET
2013-02-20 19:34             ` André Hentschel
2013-02-21 10:33               ` Will Deacon [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=20130221103342.GA20566@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matthieu.castet@parrot.com \
    --cc=nerv@dawncrow.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;
as well as URLs for NNTP newsgroup(s).