From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Christian Brauner <christian.brauner@ubuntu.com>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Qais Yousef <qais.yousef@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args
Date: Sat, 23 May 2020 21:49:58 +0200 [thread overview]
Message-ID: <6a14fbe8-b135-4e69-c2e6-dbb3d70c0afd@physik.fu-berlin.de> (raw)
In-Reply-To: <20200517151853.z6y42y4npd4plgkb@wittgenstein>
Hi!
On 5/17/20 5:18 PM, Christian Brauner wrote:
>> Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
>> ---
>> /* v2 */
>> - Christian Brauner <christian.brauner@ubuntu.com>:
>> - Continue to preserve afs.pfs in r16. I wasn't clear that r16 needs to
>> be used because switch stack and load stack rely on it being saved in
>> r16 and they'll be very unhappy when it's not. r16 is clobbered though
>> so now the mov loc1=r16 in there makes sense to me.
>> - Well, it's tested now...
>
> Tony, I managed to test this now.
Any update on this?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-05-23 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 15:16 [PATCH v2] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args Christian Brauner
2020-05-17 15:18 ` Christian Brauner
2020-05-23 19:49 ` John Paul Adrian Glaubitz [this message]
2020-05-28 19:51 ` Christian Brauner
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=6a14fbe8-b135-4e69-c2e6-dbb3d70c0afd@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=christian.brauner@ubuntu.com \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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).