From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Jamie Lokier <jamie@shareable.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: asm (lidt) question
Date: Tue, 22 Jul 2003 13:50:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307221347400.2199@chaos> (raw)
In-Reply-To: <Pine.LNX.4.55.0307221021130.1372@bigblue.dev.mcafeelabs.com>
On Tue, 22 Jul 2003, Davide Libenzi wrote:
> On Tue, 22 Jul 2003, Jamie Lokier wrote:
>
> > Davide Libenzi wrote:
> > > IMHO, since "var" is really an output parameter.
> >
> > "var" is read, not written.
> > I think you are confusing "lidt" with "sidt".
>
> Actually I don't even know what I was confusing, since L and S are not
> there for nothing ;) And yes, the form with =m as input parameter should
> be corrected, even if it generates the same code.
>
>
>
> - Davide
LIDT is "load interrupt descriptor table". SIDT is "store interrupt
descriptor table". Only SIDT modifies memory. LIDT reads from memory
and puts the result into a special CPU register, therefore doesn't
modify memory.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-07-22 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 22:28 Randy.Dunlap
2003-07-17 22:36 ` Davide Libenzi
2003-07-17 23:18 ` Davide Libenzi
2003-07-17 23:31 ` Randy.Dunlap
2003-07-17 23:36 ` Davide Libenzi
2003-07-22 17:27 ` Jamie Lokier
2003-07-22 17:31 ` Davide Libenzi
2003-07-22 17:50 ` Richard B. Johnson [this message]
2003-07-22 17:54 ` Davide Libenzi
2003-07-22 18:58 ` Randy.Dunlap
2003-07-22 18:58 ` Davide Libenzi
2003-07-22 19:04 ` Randy.Dunlap
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=Pine.LNX.4.53.0307221347400.2199@chaos \
--to=root@chaos.analogic.com \
--cc=davidel@xmailserver.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®