From: Christian Brauner <christian.brauner@ubuntu.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, 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" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args
Date: Thu, 14 May 2020 07:50:01 +0000 [thread overview]
Message-ID: <20200514075001.c63f3isbialsacpd@wittgenstein> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7F6266E0@ORSMSX115.amr.corp.intel.com>
On Wed, May 13, 2020 at 09:19:41PM +0000, Luck, Tony wrote:
> > I tried my very best to test this patch including installing Debian 3
> > and 4 to try and get my hands on a gcc version that would allow
> > cross-compiling for ia64. But no, even that wasn't possible let alone a
> > working qemu for ia64. So this is largely untested but hopefully a
> > straightforward change. If this breaks something we will hear from
> > people if they still care about new kernels on ia64 since they won't be
> > able to get any further than trying to start init. :) If this patch
> > breaks it, I'll fix it.
>
> My last functional ia64 machine no longer powers on. Unclear if it's just
> a broken power supply or something more serious. With almost nobody
> in offices/labs anymore my search for another machine is proceeding
> slowly.
Ah. :/
>
> Which is to say ... it won't be me noticing any breakage (at least not for
> a while).
If we can't get it tested on a machine soon, would you still be ok
proceeding with this patch?
>
> I think Al Viro bought an ia64 on ebay a while back ... if that's still running
> perhaps he'll test?
I have to admit, that out of pure desperation I considered buying on too
on ebay. But they are still suprisingly pricy.
Christian
prev parent reply other threads:[~2020-05-14 7:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 20:48 [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args Christian Brauner
2020-05-13 21:19 ` Luck, Tony
2020-05-13 21:26 ` John Paul Adrian Glaubitz
2020-05-14 7:46 ` Christian Brauner
2020-05-14 7:53 ` John Paul Adrian Glaubitz
2020-05-14 7:58 ` Christian Brauner
2020-05-14 8:24 ` John Paul Adrian Glaubitz
2020-05-14 8:37 ` Christian Brauner
2020-05-14 8:51 ` John Paul Adrian Glaubitz
2020-05-14 9:48 ` John Paul Adrian Glaubitz
2020-05-14 10:04 ` Christian Brauner
2020-05-14 10:08 ` John Paul Adrian Glaubitz
2020-05-14 10:15 ` Christian Brauner
2020-05-14 10:19 ` Christian Brauner
2020-05-14 10:21 ` John Paul Adrian Glaubitz
2020-05-14 10:32 ` Christian Brauner
2020-05-14 10:35 ` John Paul Adrian Glaubitz
2020-05-14 10:39 ` Christian Brauner
2020-05-14 10:37 ` Christian Brauner
2020-05-14 10:45 ` Andreas Schwab
2020-05-14 10:51 ` Christian Brauner
2020-05-14 10:37 ` Andreas Schwab
2020-05-14 13:00 ` Christian Brauner
2020-05-14 8:58 ` Sebastian Andrzej Siewior
2020-05-14 9:57 ` Christian Brauner
2020-05-14 7:50 ` Christian Brauner [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=20200514075001.c63f3isbialsacpd@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--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 \
--cc=viro@zeniv.linux.org.uk \
/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