xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 5/5] x86emul: disable FPU/MMX/SIMD insn emulation when !HVM
Date: Fri, 3 Apr 2020 09:52:28 +0200	[thread overview]
Message-ID: <8799ecd8-c27e-2d01-b236-dfa0aedefa14@suse.com> (raw)
In-Reply-To: <a016ba7f-f860-9372-caab-d9400c064fd9@citrix.com>

On 03.04.2020 00:18, Andrew Cooper wrote:
> On 20/12/2019 16:01, Andrew Cooper wrote:
>>> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>> ---
>>> I'll be happy to take suggestions allowing to avoid -Wno-unused-label.
>> I think I'm going to need a little while to figure out how this works.
> 
> So, after having had an evening playing with this, things get massively
> simpler when NO_MMX is folded with NO_SIMD.
> 
> MMX is a SIMD technology, and I can't see a compelling reason to control
> their inclusion separately.  We're either going to want everything or
> nothing.

I disagree - while MMX is a form of SIMD, what SIMD here means is
anything using the XMM register file and its extensions. Iirc
AMD once considered dropping MMX, and if I'm not mistaken early
Phi's didn't support MMX nor FPU. Hence I view a mode not
allowing MMX but allowing SIMD as a viable one to support.

> The attached incremental works for me without a single out-of-place
> label.  There is some further cleanup which can be done such as not
> making the CASE_ macros conditional.

Well, if we were to follow your alternative model - perhaps.
What I dislike though is something like the last hunk (an #ifdef
around a construct which can already abstract away things, and
which is specifically intended to avoid some #ifdef-ary).

>  (OTOH, the compile error from
> might be helpful to keep in some form).

There looks to be a word missing here, which puts me into trouble
understanding what you mean.

Jan


  reply	other threads:[~2020-04-03  7:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 13:37 [Xen-devel] [PATCH 0/5] x86emul: allow suppressing FPU/MMX/SIMD insn emulation Jan Beulich
2019-12-20 13:39 ` [Xen-devel] [PATCH 1/5] x86emul: use CASE_SIMD_PACKED_INT() where possible Jan Beulich
2019-12-20 15:35   ` Andrew Cooper
2019-12-20 13:39 ` [Xen-devel] [PATCH 2/5] x86emul: introduce CASE_SIMD_PACKED_INT_VEX() Jan Beulich
2019-12-20 15:42   ` Andrew Cooper
2019-12-20 13:40 ` [Xen-devel] [PATCH 3/5] x86emul: drop CASE_SIMD_DOUBLE_FP() Jan Beulich
2019-12-20 15:48   ` Andrew Cooper
2019-12-20 13:40 ` [Xen-devel] [PATCH 4/5] x86emul: introduce CASE_SIMD_..._FP_VEX() Jan Beulich
2019-12-20 15:49   ` Andrew Cooper
2019-12-20 13:41 ` [Xen-devel] [PATCH 5/5] x86emul: disable FPU/MMX/SIMD insn emulation when !HVM Jan Beulich
2019-12-20 16:01   ` Andrew Cooper
2019-12-20 16:20     ` Jan Beulich
2020-04-02 22:18     ` Andrew Cooper
2020-04-03  7:52       ` Jan Beulich [this message]
2020-03-24 12:10   ` [Xen-devel] Ping: " Jan Beulich

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=8799ecd8-c27e-2d01-b236-dfa0aedefa14@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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).