All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emanuele Altieri <ealtieri@hampshire.edu>
To: h-peter recktenwald <lx@lxhp.in-berlin.de>
Cc: Linux Assembly List <linux-assembly@vger.kernel.org>
Subject: Re: i386: far jumps
Date: 22 Jul 2002 16:16:42 -0400	[thread overview]
Message-ID: <1027369002.1952.14.camel@italia> (raw)
In-Reply-To: <20020719174410.7c8f0d1f.lx@lxhp.in-berlin.de>

On Fri, 2002-07-19 at 13:44, h-peter recktenwald wrote:
> On 15 Jul 2002 22:21:26 -0400
> Emanuele Altieri <ealtieri@hampshire.edu> wrote:
> 
> > Greetings,
> > 
> > I'm doing some experiments with far jumps to different code segments.
> > For example:
> > 
> >    ljmp *%fs:hello
> > 
> > I get a general protection error. I don't understand why. I believe it's
> > a notation error. Can anybody see it?
> > 
> > I'm interested in this because I need the segment argument of ljmp to be
> 
> 	Linux?

No (/ not yet). I'm just experimenting on Intel's segmentation and task
support with a small OS that I created for this purpose. I'm using GCC
and GAS to implement it.

By the way, I found a workaround to the ljmp problem:

    pushw <segment>
    pushl <offset>
    lret

For example

    pushw $16
    pushl $hello
    lret

This is equivalent to "ljmp $16, $hello", but now the segment and offset
arguments do not need to be constants.


  -Emanuele


      reply	other threads:[~2002-07-22 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16  2:21 i386: far jumps Emanuele Altieri
2002-07-19 17:44 ` h-peter recktenwald
2002-07-22 20:16   ` Emanuele Altieri [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=1027369002.1952.14.camel@italia \
    --to=ealtieri@hampshire.edu \
    --cc=linux-assembly@vger.kernel.org \
    --cc=lx@lxhp.in-berlin.de \
    /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.