qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] minor x86-64 corrections
Date: Fri, 21 Jan 2005 22:44:50 +0100	[thread overview]
Message-ID: <41F177D2.6040809@bellard.org> (raw)
In-Reply-To: <41F1670C.2060805@volny.cz>

Filip Navara wrote:
> Changelog:
> 
> 2005-01-21 Filip Navara <navaraf@reactos.com>
> 
> * Add support for CR8 register.
> * Don't throw exception when assigning zero to SS register
> in 64-bit mode.
> 
> BTW, the callgate support for x86-64 in long mode is broken. See "AMD64 
> Architecture Programmer’s Manual Volume 3: General-Purpose and System 
> Instructions", page 90. Anybody cares to fix it?

No time yet. It would be interesting to find the problem for the Linux 
user code too.

> --- target-i386/helper.c	16 Jan 2005 23:35:43 -0000	1.40
> +++ target-i386/helper.c	21 Jan 2005 20:13:30 -0000
> @@ -1454,8 +1454,13 @@
>      selector &= 0xffff;
>      if ((selector & 0xfffc) == 0) {
>          /* null selector case */
> -        if (seg_reg == R_SS)
> +        if (seg_reg == R_SS) {
> +#ifdef TARGET_X86_64
> +            if (env->hflags & HF_CS64_MASK)
> +                return;
> +#endif
>              raise_exception_err(EXCP0D_GPF, 0);
> +        }
>          cpu_x86_load_seg_cache(env, seg_reg, selector, 0, 0, 0);

Maybe the SS segment cache should be set to zero ?

> +void OPPROTO op_movtl_T0_cr7(void)
> +{
> +    T0 = (cpu_get_apic_tpr(env) & 0xf) >> 4;
> +}

Why do you call it cr7 ?

Fabrice.

  reply	other threads:[~2005-01-21 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 20:33 [Qemu-devel] [PATCH] minor x86-64 corrections Filip Navara
2005-01-21 21:44 ` Fabrice Bellard [this message]
2005-01-21 22:07   ` Filip Navara
2005-01-21 22:27     ` Filip Navara
  -- strict thread matches above, loose matches on Subject: below --
2005-01-23 10:35 Filip Navara

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=41F177D2.6040809@bellard.org \
    --to=fabrice@bellard.org \
    --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 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).