All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael McConnell <soruk@eridani.co.uk>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: MAINTAINERS file out of date?
Date: Thu, 26 Apr 2007 22:16:43 -0700	[thread overview]
Message-ID: <4631873B.1000107@zytor.com> (raw)
In-Reply-To: <m1647ijvk1.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> WANG Cong <xiyou.wangcong@gmail.com> writes:
> 
>> Thanks for your point. 
>> I know little about virtualization, maybe can't help much. But I am interested
>> in other things you mentioned. AFAIK, segments can't be avoided on i386, and
>> Linux uses them very little, how are they recalculated constantly?
> 
> Look in arch/i386/boot/setup.S it runs in 16bit mode.  We are talking about
> real mode segments not 16bit segments.
> 
> 16bit real mode is a completely different ball game, and why we keep BIOS
> calls isolated to that one dinky file.
> 

A lot of that code (although, of course, not all) could be written in C,
though.  I'm thinking of taking a stab at rewriting it that way.

	-hpa

  reply	other threads:[~2007-04-27  5:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 22:19 MAINTAINERS file out of date? Michael McConnell
2007-04-26 23:13 ` H. Peter Anvin
2007-04-27  1:09   ` WANG Cong
2007-04-27  1:12     ` H. Peter Anvin
2007-04-27  2:32       ` WANG Cong
2007-04-27  4:22         ` Eric W. Biederman
2007-04-27  5:16           ` H. Peter Anvin [this message]
2007-04-27  5:24             ` Eric W. Biederman
2007-04-27  5:27               ` H. Peter Anvin
2007-04-27 10:28                 ` WANG Cong
2007-04-27 15:55                   ` H. Peter Anvin
2007-04-27 10:34             ` Andi Kleen
2007-04-27 15:56               ` H. Peter Anvin
2007-04-27 17:02                 ` Eric W. Biederman

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=4631873B.1000107@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soruk@eridani.co.uk \
    /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.