qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] target-i386: get CPL from SS.DPL
Date: Wed, 21 May 2014 13:13:21 +0200	[thread overview]
Message-ID: <537C8A51.2080008@redhat.com> (raw)
In-Reply-To: <20140520215433.GA19697@morn.localdomain>

Il 20/05/2014 23:54, Kevin O'Connor ha scritto:
> On Fri, May 16, 2014 at 09:59:25PM +0200, Paolo Bonzini wrote:
>> CS.RPL is not equal to the CPL in the few instructions between
>> setting CR0.PE and reloading CS.  We get this right in the common
>> case, because writes to CR0 do not modify the CPL, but it would
>> not be enough if an SMI comes exactly during that brief period.
>> Were this to happen, the RSM instruction would erroneously set
>> CPL to the low two bits of the real-mode selector; and if they are
>> not 00, the next instruction fetch cannot access the code segment
>> and causes a triple fault.
>>
>> However, SS.DPL *is* always equal to the CPL.  In real processors
>> (AMD only) there is a weird case of SYSRET setting SS.DPL=SS.RPL
>> from the STAR register while forcing CPL=3, but we do not emulate
>> that.
>
> I was in the process of testing something else, when I encountered a
> problem with an old MSDOS 6.22 floppy I had.  I tracked it down to an
> error in one of the commits I did in this series (I sent a fix in a
> separate email for it).
>
> Unfortunately, after I fixed the problem in my patch, your patch above
> breaks it again.  I think it's another VM86 thing.
>
> Steps to reproduce:
>
> 1 - grab the DOS 6.22 floppy from: http://bootdisk.com/bootdisk.htm
>
> 2 - boot it up and add emm386.exe to config.sys ("edit config.sys" and
> add "DEVICE=EMM386.EXE" on the second line of the file).
>
> 3 - reboot with modified config.sys

I cannot reproduce this.  I can see the breakage with current master, 
and I can see your patch fixing it.  It keeps working with these 
changes.  Please try branch cpl-queue at 
git://github.com/bonzini/qemu.git and see if it works for you too.

My QEMU command line is simply "-fda boot622.img".

Paolo

  reply	other threads:[~2014-05-21 11:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 19:59 [Qemu-devel] [PATCH v2 0/3] target-i386: fix CPL computation Paolo Bonzini
2014-05-16 19:59 ` [Qemu-devel] [PATCH 1/3] target-i386: fix segment flags for SMM, user-mode emulation and VM86 mode Paolo Bonzini
2014-05-16 19:59 ` [Qemu-devel] [PATCH 2/3] target-i386: rework CPL checks during task switch, preparing for next patch Paolo Bonzini
2014-05-16 19:59 ` [Qemu-devel] [PATCH 3/3] target-i386: get CPL from SS.DPL Paolo Bonzini
2014-05-20 21:54   ` Kevin O'Connor
2014-05-21 11:13     ` Paolo Bonzini [this message]
2014-05-21 14:05       ` Kevin O'Connor
2014-05-21 14:18         ` Paolo Bonzini
2014-05-21 14:31           ` Kevin O'Connor
  -- strict thread matches above, loose matches on Subject: below --
2014-05-15 16:56 [Qemu-devel] [PATCH 0/3] target-i386: fix CPL computation Paolo Bonzini
2014-05-15 16:56 ` [Qemu-devel] [PATCH 3/3] target-i386: get CPL from SS.DPL Paolo Bonzini
2014-05-15 18:38   ` Kevin O'Connor
2014-05-16  7:35     ` Paolo Bonzini

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=537C8A51.2080008@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kevin@koconnor.net \
    --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).