public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: DPMI errors on amd64, but not on i386
Date: Fri, 06 Feb 2009 22:10:27 +0100	[thread overview]
Message-ID: <498CA743.3070604@zgod.cjb.net> (raw)
In-Reply-To: <gmi742$7hd$1@ger.gmane.org>

Javier wrote:
> Julius Schwartzenberg wrote:
>> I'm getting similar results with DPMI on AMD64. According to dosemu.conf
>> DMPI on AMD64 is experimental, so I guess this is to be expected. I have
>> the same problem when CPUEMU is set to full though, so I guess the CPU
>> emulation is also still experimental.
> 
> Please note that I am using the 32-bit binary on both the x86_32 and 64 
> kernel -- I've no knowledge about how dosemu works, but does it follow a
> diferent code path on amd64 even if compiled for i386? (apart from 
> x86_64's missing vm86plus syscall). 
> Because of this, I initially believed I had misconfigured my kernel 
> build, but since I am also having problems with the default 64-bit Debian 
> kernel I guess not.

I suspect the experimental limitation doesn't come from the 32 or 64 bit 
binary, but from the 64-bits kernel. I understand certain 16-bit mode 
things aren't possible when the system runs in 64-bit mode, so that's 
why the emulation is necessary for certain parts then. This emulation 
feature is still experimental.

  reply	other threads:[~2009-02-06 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 20:24 DPMI errors on amd64, but not on i386 Javier
2009-02-06 17:19 ` Julius Schwartzenberg
2009-02-06 20:38   ` Javier
2009-02-06 21:10     ` Julius Schwartzenberg [this message]
     [not found]       ` <498CAC15.9080905@pobox.com>
2009-02-07 21:47         ` Julius Schwartzenberg

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=498CA743.3070604@zgod.cjb.net \
    --to=julius@zgod.cjb.net \
    --cc=linux-msdos@vger.kernel.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