All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Richard Henderson" <rth@twiddle.net>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
	"Thomas Huth" <thuth@redhat.com>,
	"Cornelia Huck" <cohuck@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH RFC 2/2] tests/tcg: target/s390: Add test for VECTOR LOAD GR FROM VR ELEMENT
Date: Thu, 28 Feb 2019 08:11:38 +0100	[thread overview]
Message-ID: <90c21734-878e-9c0a-cea3-911c4931e8cd@redhat.com> (raw)
In-Reply-To: <bd3c9d75-ab17-cd04-ba04-cb1fb19b4ce8@twiddle.net>

On 28.02.19 01:24, Richard Henderson wrote:
> On 2/27/19 1:40 PM, Alex Bennée wrote:
>> And crucially have nice regular sized instructions. Is that not an option?
> 
> s390 insns are {2,4,6} bytes.  I don't think that there's an easy way to pick
> out the hw status codes that would give the ilen of the faulting insn.
> 

We would have to read the faulting instruction to determine based on the
two leftmost bits the ilen. But I don't consider that approach much
cleaner compared to signal + setjmp (signal + sigsetjmp after I fixed it
;) )

Thanks for the pointer though, Alex

> 
> r~
> 


-- 

Thanks,

David / dhildenb

  reply	other threads:[~2019-02-28  7:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 11:14 [Qemu-devel] [PATCH RFC 0/2] tests/tcg: Vector instruction tests for target/s390x David Hildenbrand
2019-02-27 11:14 ` [Qemu-devel] [PATCH RFC 1/2] tests/tcg: Allow targets to set the optimization level David Hildenbrand
2019-02-27 11:46   ` Alex Bennée
2019-02-27 11:58     ` David Hildenbrand
2019-02-27 12:42     ` David Hildenbrand
2019-02-27 13:44       ` David Hildenbrand
2019-02-28  0:26   ` Richard Henderson
2019-02-27 11:14 ` [Qemu-devel] [PATCH RFC 2/2] tests/tcg: target/s390: Add test for VECTOR LOAD GR FROM VR ELEMENT David Hildenbrand
2019-02-27 11:19   ` David Hildenbrand
2019-02-27 19:37   ` David Hildenbrand
2019-02-27 20:19     ` Alex Bennée
2019-02-27 20:20       ` David Hildenbrand
2019-02-27 21:40         ` Alex Bennée
2019-02-28  0:24           ` Richard Henderson
2019-02-28  7:11             ` David Hildenbrand [this message]
2019-02-28  0:17     ` Richard Henderson
2019-02-28  7:14       ` David Hildenbrand
2019-02-28 17:39         ` Richard Henderson

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=90c21734-878e-9c0a-cea3-911c4931e8cd@redhat.com \
    --to=david@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.