From: Richard Henderson <richard.henderson@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] user-exec: Do not filter the signal on si_code
Date: Tue, 1 Oct 2019 07:58:30 -0700 [thread overview]
Message-ID: <b2496351-b7ae-55e7-611c-4e7eda48c02b@linaro.org> (raw)
In-Reply-To: <ba9c069b-fb56-2438-07f9-bb0c5eb97058@vivier.eu>
On 10/1/19 6:15 AM, Laurent Vivier wrote:
> Le 01/10/2019 à 13:46, Peter Maydell a écrit :
>> On Tue, 1 Oct 2019 at 12:19, Laurent Vivier <laurent@vivier.eu> wrote:
>>> Is it possible to update the farm to Centos 8?
>>>
>>> Or as the kernel involved is specifically for POWER9, is it possible to
>>> use only POWER8?
>>
>> My experience is that the gcc cfarm admins aren't in
>> principle against the idea of upgrading farm machines,
>> but in practice they tend to have a shortage of effort.
>> If there's a centos-7-kernel-update package that could
>> be installed without doing a full distro upgrade that
>> would probably be pretty easy to ask them to arrange.
>
> It seems Centos provides a 4.18 kernel for POWER9 on Centos 7:
>
> http://mirror.centos.org/altarch/7/os/power9/Packages/kernel-4.18.0-80.7.2.el7.ppc64le.rpm
Thanks guys. I've sent a message to the admins asking for an update on gcc135.
r~
prev parent reply other threads:[~2019-10-01 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 19:29 [PATCH] user-exec: Do not filter the signal on si_code Richard Henderson
2019-09-30 19:40 ` no-reply
2019-09-30 21:01 ` Richard Henderson
2019-10-01 10:34 ` Peter Maydell
2019-10-01 11:19 ` Laurent Vivier
2019-10-01 11:46 ` Peter Maydell
2019-10-01 13:15 ` Laurent Vivier
2019-10-01 14:58 ` Richard Henderson [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=b2496351-b7ae-55e7-611c-4e7eda48c02b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).