qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rth7680@gmail.com, leon.alrae@imgtec.com,
	agraf@suse.de, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH v4 4/5] target-i386: fix memory operations in helpers
Date: Wed, 1 Jul 2015 10:17:27 +0100	[thread overview]
Message-ID: <5593B027.8070102@twiddle.net> (raw)
In-Reply-To: <20150629072333.388.3004.stgit@PASHA-ISP>

On 06/29/2015 08:23 AM, Pavel Dovgalyuk wrote:
> This patch passes TB return address into softmmu functions that are
> invoked from target helpers. This allows correct PC and icount recovering
> while handling MMU faults.
>
> Signed-off-by: Pavel Dovgalyuk<pavel.dovgaluk@ispras.ru>
> ---
>   target-i386/cc_helper.c   |    2
>   target-i386/cpu.h         |    5
>   target-i386/excp_helper.c |   21 +
>   target-i386/fpu_helper.c  |  146 +++++----
>   target-i386/helper.c      |    4
>   target-i386/int_helper.c  |   32 +-
>   target-i386/mem_helper.c  |   39 +-
>   target-i386/misc_helper.c |   12 -
>   target-i386/ops_sse.h     |    2
>   target-i386/seg_helper.c  |  712 +++++++++++++++++++++++----------------------
>   target-i386/svm_helper.c  |    4
>   target-i386/translate.c   |   25 --
>   12 files changed, 503 insertions(+), 501 deletions(-)

This patch is too big.  It really needs to be split into several patches.

(1) Introduce raise_exception_ra that accepts the GETPC argument, so that
     (a) you can stage the changes in and
     (b) most of the seg_helper changes from do_interrupt et al
         aren't needed.

(2) Stage in fixes for each of the (groups of) helpers callable from
     translate.c.  E.g. fld, fst in one group, division in another.

And while this patch set fixes icount, do you have any evidence that we ever 
got incorrect PC values handling mmu faults?


r~

  reply	other threads:[~2015-07-01  9:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29  7:23 [Qemu-devel] [PATCH v4 0/5] Fix exceptions handling for MIPS and i386 Pavel Dovgalyuk
2015-06-29  7:23 ` [Qemu-devel] [PATCH v4 1/5] softmmu: add helper function to pass through retaddr Pavel Dovgalyuk
2015-07-01  9:00   ` Richard Henderson
2015-07-01 16:16   ` Aurelien Jarno
2015-06-29  7:23 ` [Qemu-devel] [PATCH v4 2/5] cpu-exec: introduce loop exit with restore function Pavel Dovgalyuk
2015-07-01  9:02   ` Richard Henderson
2015-07-01 16:30   ` Aurelien Jarno
2015-06-29  7:23 ` [Qemu-devel] [PATCH v4 3/5] target-mips: improve exceptions handling Pavel Dovgalyuk
2015-07-01 16:37   ` Aurelien Jarno
2015-06-29  7:23 ` [Qemu-devel] [PATCH v4 4/5] target-i386: fix memory operations in helpers Pavel Dovgalyuk
2015-07-01  9:17   ` Richard Henderson [this message]
2015-07-01  9:22     ` Pavel Dovgaluk
2015-07-01  9:26       ` Richard Henderson
2015-06-29  7:23 ` [Qemu-devel] [PATCH v4 5/5] target-ppc: exceptions handling in icount mode Pavel Dovgalyuk
2015-06-29  7:24 ` [Qemu-devel] [PATCH v4 0/5] Fix exceptions handling for MIPS and i386 Pavel Dovgaluk

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=5593B027.8070102@twiddle.net \
    --to=rth@twiddle.net \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth7680@gmail.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).