From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 07/10] target-s390x: enable fully implemented facilities
Date: Mon, 25 May 2015 23:04:15 +0200 [thread overview]
Message-ID: <55638E4F.4090101@suse.de> (raw)
In-Reply-To: <20150525210219.GA28739@aurel32.net>
On 25.05.15 23:02, Aurelien Jarno wrote:
> On 2015-05-25 22:39, Alexander Graf wrote:
>>
>>
>> On 25.05.15 01:47, Aurelien Jarno wrote:
>>> Cc: Alexander Graf <agraf@suse.de>
>>> Cc: Richard Henderson <rth@twiddle.net>
>>> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>>
>> Shouldn't this get populated based on the selected -cpu type?
>
> In the long term yes, but given we only implement one CPU type (or
> rather none) in TCG mode, we can consider that's already the case.
There are patches coming from IBM to at least add a list of a good
number of s390x cpu types. I'd really like to make use of that and have
actual CPU types selectable.
At least let's move towards that model. So the code in question should
take the facility capabilities from the first cpu object (or the class?)
for example and we bump it to the currently supported feature set in there.
Alex
next prev parent reply other threads:[~2015-05-25 21:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 23:47 [Qemu-devel] [PATCH 00/10] target-s390x: TCG fixes and improvements Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 01/10] target-s390x: fix PSW value on dynamical exception from helpers Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 02/10] target-s390x: fix MMU index computation Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 03/10] target-s390x: define default NaN values Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 04/10] target-s390x: silence NaNs for LOAD LENGTHENED and LOAD ROUNDED Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 05/10] target-s390x: detect tininess before rounding for FP operations Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 06/10] target-s390x: improve facilities list Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 07/10] target-s390x: enable fully implemented facilities Aurelien Jarno
2015-05-25 20:39 ` Alexander Graf
2015-05-25 21:02 ` Aurelien Jarno
2015-05-25 21:04 ` Alexander Graf [this message]
2015-05-25 21:13 ` Aurelien Jarno
2015-05-25 21:47 ` Alexander Graf
2015-05-26 6:02 ` Aurelien Jarno
2015-05-26 8:29 ` Alexander Graf
2015-05-26 9:05 ` Aurelien Jarno
2015-05-26 10:19 ` Alexander Graf
2015-05-24 23:47 ` [Qemu-devel] [PATCH 08/10] target-s390x: implement STFLE instruction Aurelien Jarno
2015-05-25 23:08 ` Richard Henderson
2015-05-25 23:14 ` Alexander Graf
2015-05-26 6:03 ` Aurelien Jarno
2015-05-26 16:00 ` Richard Henderson
2015-05-26 22:03 ` Aurelien Jarno
2015-05-27 14:31 ` Richard Henderson
2015-05-27 14:55 ` Alexander Graf
2015-05-27 15:57 ` Aurelien Jarno
2015-05-28 1:55 ` Alexander Graf
2015-05-24 23:47 ` [Qemu-devel] [PATCH 09/10] target-s390x: move a few instructions to the correct facility Aurelien Jarno
2015-05-24 23:47 ` [Qemu-devel] [PATCH 10/10] target-s390x: implement LAY and LAEY instructions Aurelien Jarno
2015-05-28 22:03 ` [Qemu-devel] [PATCH 00/10] target-s390x: TCG fixes and improvements Alexander Graf
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=55638E4F.4090101@suse.de \
--to=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).