From: Greg KH <gregkh@linuxfoundation.org>
To: "André Hentschel" <nerv@dawncrow.de>
Cc: linux-arch@vger.kernel.org, will.deacon@arm.com,
rmk+kernel@arm.linux.org.uk
Subject: Re: arm: Request to preserve TPIDRURW per thread
Date: Mon, 21 Jan 2013 16:11:43 -0800 [thread overview]
Message-ID: <20130122001143.GA4107@kroah.com> (raw)
In-Reply-To: <50FDD7A8.1080402@dawncrow.de>
On Tue, Jan 22, 2013 at 01:04:56AM +0100, André Hentschel wrote:
> Hi,
> that comes a bit late, but [1] asked for objections.
> As you can see in [2] there are more and more applications coming to WinRT, Wine could support them,
> but mostly they expect to have the thread environment block (TEB) in TPIDRURW.
> This register must be preserved per thread and we have patches for that.
>
> Currently there exist two kernel behaviours:
>
> 1. the kernel does not touch TPIDRURW at all ("covert channel")
> 2. the kernel clears TPIDRURW on thread switch
>
> Attached to [3] you'll find kernel patches you can freely use.
> Permission and more info you'll find in [4].
> Any hints or suggestions?
>
> [1] http://www.kernelhub.org/?p=2&msg=57979
> [2] http://forum.xda-developers.com/showthread.php?t=2092348
> [3] http://bugs.winehq.org/show_bug.cgi?id=31322
> [4] http://bugs.winehq.org/show_bug.cgi?id=31308
Please submit the patches to fix this in the way described in
Documentation/SubmittingPatches. Once they are in Linus's tree, I'll be
glad to take them in the stable tree if they meet the guidelines that
are described in Documentation/stable_kernel_rules.txt.
Does that help?
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-22 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 0:04 arm: Request to preserve TPIDRURW per thread André Hentschel
2013-01-22 0:11 ` Greg KH [this message]
2013-01-22 0:16 ` André Hentschel
2013-01-22 9:24 ` Will Deacon
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=20130122001143.GA4107@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=nerv@dawncrow.de \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).