qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Ricky Zhou <ricky@rzhou.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com
Subject: Re: [PATCH] target/i386: Fix exception classes for SSE/AVX instructions.
Date: Fri, 14 Apr 2023 17:19:18 +0200	[thread overview]
Message-ID: <f337c4f5-4a20-cc29-033c-c5766f9c96f6@linaro.org> (raw)
In-Reply-To: <20230212082812.55101-1-ricky@rzhou.org>

Hi Ricky,

On 12/2/23 09:28, Ricky Zhou wrote:
> Fix the exception classes for some SSE/AVX instructions to match what is
> documented in the Intel manual.
> 
> Most of these changes have no functional effect on the behavior that
> qemu implements (primarily >= 16-byte memory alignment checks). For
> example, since qemu does not implement the AC flag, there is no
> difference in behavior between Exception Classes 4 and 5 for
> instructions where the SSE version only takes <16 byte memory operands.

Having this patch split in 2 (documentation first, logical change then)
would ease code review.

> There is one functional change:
> 
> Before this change, MOVNTPS and MOVNTPD were labeled as Exception Class
> 4 (only requiring alignment for legacy SSE instructions). This changes
> them to Exception Class 1 (always requiring memory alignment), as
> documented in the Intel manual.

This could be a 3rd patch.

> Signed-off-by: Ricky Zhou <ricky@rzhou.org>
> ---
>   target/i386/tcg/decode-new.c.inc | 79 ++++++++++++++++----------------
>   1 file changed, 40 insertions(+), 39 deletions(-)

Regards,

Phil.


  parent reply	other threads:[~2023-04-14 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12  8:28 [PATCH] target/i386: Fix exception classes for SSE/AVX instructions Ricky Zhou
2023-03-20 13:21 ` Ricky Zhou
2023-04-14  7:45   ` Ricky Zhou
2023-04-14 15:19 ` Philippe Mathieu-Daudé [this message]
2023-05-01 11:19   ` Ricky Zhou

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=f337c4f5-4a20-cc29-033c-c5766f9c96f6@linaro.org \
    --to=philmd@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ricky@rzhou.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).