From: Christian Borntraeger <borntraeger@de.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org
Cc: thuth@redhat.com, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH] target/s390x: Implement CSST
Date: Mon, 19 Jun 2017 14:33:10 +0200 [thread overview]
Message-ID: <9362010b-5c05-c29f-6e67-c182d2ae57ec@de.ibm.com> (raw)
In-Reply-To: <429793f7-a3c1-91ec-9a83-908ee779e703@redhat.com>
On 06/19/2017 02:05 PM, David Hildenbrand wrote:
> On 19.06.2017 12:03, David Hildenbrand wrote:
>> On 15.06.2017 22:37, Richard Henderson wrote:
>>> There are no uses in a Linux system with which to test,
>>> but it Looks Right by my reading of the PoO.
>>
>> I am using next.git/master with this patch applied:
>> https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features&id=8aa8680aa383bf6e2ac
>>
>> I am using QEMU with the mvcos patch and your patch applied (and a patch
>> that allows enabling csst/csst2).
>>
>> I am using the following qemu command line:
>>
>> #!/bin/bash
>> /home/dhildenb/git/qemu/s390x-softmmu/qemu-system-s390x \
>> -nographic -nodefaults -machine s390-ccw-virtio,accel=tcg \
>> -cpu qemu,mvcos=on,stfle=on,ldisp=on,ldisphp=on,\
>> eimm=on,stckf=on,csst=on,csst2=on,ginste=on,exrl=on\
>> -m 256M -smp 1 -chardev stdio,id=con0 \
>> -device sclpconsole,chardev=con0 \
>> -kernel vmlinux -initrd /home/dhildenb/initrd.debian
>>
>> Right now, I can start a z9 compiled kernel.
>>
>> When trying to start a z10 compiled kernel (which generates many csst),
I would be very surprised if the kernel would contain any csst. gcc does not
emit csst and the kernel source also does not contain it.
next prev parent reply other threads:[~2017-06-19 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 20:37 [Qemu-devel] [PATCH] target/s390x: Implement CSST Richard Henderson
2017-06-19 8:08 ` Thomas Huth
2017-06-19 15:20 ` Richard Henderson
2017-06-19 23:44 ` Richard Henderson
2017-06-20 4:58 ` Thomas Huth
2017-06-19 10:03 ` David Hildenbrand
2017-06-19 12:05 ` David Hildenbrand
2017-06-19 12:33 ` Christian Borntraeger [this message]
2017-06-19 12:41 ` David Hildenbrand
2017-06-19 12:47 ` Christian Borntraeger
2017-06-19 12:52 ` David Hildenbrand
2017-06-19 13:00 ` Christian Borntraeger
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=9362010b-5c05-c29f-6e67-c182d2ae57ec@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=aurelien@aurel32.net \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).