All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] kvm-x86: Remove eflags conversion into	emulator format
Date: Mon, 26 Jan 2009 14:33:19 -0600	[thread overview]
Message-ID: <497E1E0F.2060506@us.ibm.com> (raw)
In-Reply-To: <497DFC38.6040402@siemens.com>

Jan Kiszka wrote:
> It seems that the conversion of the kernel-delivered eflags state into
> qemu's internal split representation was once needed in an older kvm
> design (register read-back may have taken place from inside cpu_exec).
> Today it is plain wrong and causes incorrect cpu state reporting (gdb,
> monitor) and should also corrupt its saving (savevm, migration). Drop
> the related lines.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>   

Applied.  Thanks.

Regards,

Anthony Liguori

> ---
>
>  target-i386/kvm.c |    4 ----
>  1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 88c3137..47723f2 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -446,10 +446,6 @@ static int kvm_get_sregs(CPUState *env)
>              }
>      }
>      env->hflags = (env->hflags & HFLAG_COPY_MASK) | hflags;
> -    env->cc_src = env->eflags & (CC_O | CC_S | CC_Z | CC_A | CC_P | CC_C);
> -    env->df = 1 - (2 * ((env->eflags >> 10) & 1));
> -    env->cc_op = CC_OP_EFLAGS;
> -    env->eflags &= ~(DF_MASK | CC_O | CC_S | CC_Z | CC_A | CC_P | CC_C);
>  
>      return 0;
>  }
>
>
>
>   

      reply	other threads:[~2009-01-26 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 18:08 [Qemu-devel] [PATCH] kvm-x86: Remove eflags conversion into emulator format Jan Kiszka
2009-01-26 20:33 ` Anthony Liguori [this message]

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=497E1E0F.2060506@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.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 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.