public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [CRIU][PATCH 0/7] Add architecture support for s390x
Date: Fri, 30 Jun 2017 14:41:20 +0000	[thread overview]
Message-ID: <20170630164120.0e1a2aef@TP-holzheu> (raw)
In-Reply-To: <0003e239-f4d9-124a-fcd5-591b07b27b7e@virtuozzo.com>

Am Thu, 29 Jun 2017 17:33:51 +0300
schrieb Pavel Emelyanov <xemul@virtuozzo.com>:

> On 06/29/2017 05:23 PM, Michael Holzheu wrote:
> > Am Thu, 29 Jun 2017 12:48:28 +0300
> > schrieb Pavel Emelyanov <xemul@virtuozzo.com>:
> > 
> >> On 06/28/2017 07:11 PM, Michael Holzheu wrote:
> >>> Hello CRIU mailing list,
> >>>
> >>> This set of patches adds the s390x (64 bit mainframe) backend support to
> >>> the CRIU checkpoint/restore tool.
> >>
> >> That's really cool :) thanks a lot!
> >>
> >> There's one, quite big, thing I'd like to discuss :) So far the most active community
> >> members are x86 guys, but we already have 3 more arches (arm, aarch64 and ppc64le). 
> >> In order not to break non-x86 heavily we've set up travis-ci jobs to constantly check
> >> that criu compiles on non-x64 [1]. Also we have arm box and access to ppc64 VM from 
> >> IBM and a set of jenkins jobs [2] that run tests on them.
> >>
> >> Would you also at least add the former piece, so that we don't break compilation of your
> >> code. And ideally, we'd like to have the latter thing too.
> > 
> > Yesterday we tried to setup the travis qemu stuff, but for some reason
> > this failed. I attached our current patch to this E-mail.
> 
> OK. So we'll at least have the compilation checker :)

I just learned that qemu on s390x can only emulate older z900 mainframe machines.
Very likely the Travis Ubuntu Docker image for s390 uses newer instructions,
which is probably the reason why it currently does not work.

Michael

           reply	other threads:[~2017-06-30 14:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0003e239-f4d9-124a-fcd5-591b07b27b7e@virtuozzo.com>]

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=20170630164120.0e1a2aef@TP-holzheu \
    --to=holzheu@linux.vnet.ibm.com \
    --cc=linux-s390@vger.kernel.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