From: "H. Peter Anvin" <hpa@zytor.com>
To: Etienne Lorrain <etienne_lorrain@yahoo.fr>
Cc: Chuck Ebbert <cebbert@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: RE : Re: RE : Re: x86 setup code rewrite in C - revised
Date: Mon, 16 Jul 2007 02:15:00 -0700 [thread overview]
Message-ID: <469B3714.80105@zytor.com> (raw)
In-Reply-To: <217644.17566.qm@web26902.mail.ukl.yahoo.com>
Etienne Lorrain wrote:
> BUGS: some implementations (including the original IBM PC) have a bug which
> destroys BP
> the Trident TVGA8900CL (BIOS dated 1992/9/8) clears DS to 0000h when
> scrolling in an SVGA mode (800x600 or higher)
"When scrolling in an SVGA mode", sounds to me like a bug when using
BIOS for text output in graphics mode. We don't do that.
>>>>>> Also, I do not know if "m" is right in here:
>>>>>> static inline u8 rdfs8(addr_t addr)
>>>>>> {
>>>>>> u8 v;
>>>>>> asm("movb %%fs:%1,%0" : "=r" (v) : "m" (*(u8 *)addr));
>>>>>> return v;
>>>>>> }
>>>> The "m" is correct right there.
>>> strange, "g" would mean anything can go there - and this assembly instruction
>>> should accept every access modes.
>> Not with an %fs: prefix. It would also allow the compiler to do a move
>> into a register "on its own", which would be disastrous, since it would
>> lack the prefix. So "m" is correct.
>
> "mov %fs:(%ebx,%eax,4),%ecx" works for me.
That's an example on what "m" can generate.
"g" could produce stuff like:
mov %fs:$1234,%ecx
mov %fs:%eax,%ecx
-hpa
next prev parent reply other threads:[~2007-07-16 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 14:25 x86 setup code rewrite in C - revised Etienne Lorrain
2007-07-13 16:35 ` Chuck Ebbert
2007-07-13 16:51 ` H. Peter Anvin
2007-07-13 20:10 ` RE : " Etienne Lorrain
2007-07-13 21:19 ` H. Peter Anvin
2007-07-16 9:02 ` RE : " Etienne Lorrain
2007-07-16 9:15 ` H. Peter Anvin [this message]
2007-07-16 10:21 ` Etienne Lorrain
2007-07-13 23:09 ` RE : " Linus Torvalds
2007-07-13 22:23 ` H. Peter Anvin
2007-07-16 13:31 ` Etienne Lorrain
2007-07-16 17:35 ` H. Peter Anvin
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=469B3714.80105@zytor.com \
--to=hpa@zytor.com \
--cc=cebbert@redhat.com \
--cc=etienne_lorrain@yahoo.fr \
--cc=linux-kernel@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