9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [GSOC] plan9 which arch code to use?
Date: Tue,  6 May 2014 20:40:29 -0400	[thread overview]
Message-ID: <690893a06bbadd835f847e3f9faf741a@brasstown.quanstro.net> (raw)
In-Reply-To: <CAAVq3rn=zGE-BJivyyi9Ht6E=HTn8+khtwszPAzpJpbqrizg9w@mail.gmail.com>

On Tue May  6 18:26:58 EDT 2014, ccuiyyan@gmail.com wrote:

> Dear all,
>
>      I was confused by one experiment which is done today.
> My machine is x86_64 and I run Plan9 inside KVM. According to my
> understanding, operating system should detect which hardware platform it is
> running (x86, sparc, etc) and automatically invoke
> corresponding arch-dependent codes. But, when I echo $cputypes,
> it is 386! I also browse some kernel config file in /sys/src/9/pc, it seems
> that plan9 forces to use 386 for Intel cpus (right?). Please tolerate if I
> made stupid mistakes, I just wonder how to make a amd64 kernel? (My
> hardware already supports that.)

good question.  /sys/src/9/pc is a 386 kernel.  it runs 386 code on anything
that at least supports a 386 regardless of the hardware support.  if you
think about it, supporting more than one instruction set with a single
kernel has some added difficulties.

as cinap mentions, for a 64-bit kernel, your options are 9atom or 9front.
since i work with 9atom, i'll speak to it.  you can just install 64-bit with
no muss or fuss, if the hardware is supported.  let me know if there are
issues.  if you already have something working, then nevermind.  :-)

- erik



  parent reply	other threads:[~2014-05-07  0:40 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 21:00 yan cui
2014-05-06 21:33 ` cinap_lenrek
2014-05-06 21:48   ` yan cui
2014-05-06 21:47 ` Charles Forsyth
2014-05-06 21:53   ` yan cui
2014-05-06 21:56   ` Charles Forsyth
2014-05-06 21:59     ` Charles Forsyth
2014-05-06 22:02       ` cinap_lenrek
2014-05-06 22:05       ` Charles Forsyth
2014-05-07  5:14         ` lucio
2014-05-07  5:38           ` David du Colombier
2014-05-07  6:59             ` lucio
2014-05-07  8:38               ` Riddler
2014-05-07  8:59                 ` Charles Forsyth
2014-05-07  9:05             ` erik quanstrom
2014-05-07  9:10               ` Charles Forsyth
2014-05-07  9:16                 ` erik quanstrom
2014-05-07  9:42                 ` erik quanstrom
2014-05-07  9:23               ` David du Colombier
2014-05-07  9:25                 ` erik quanstrom
2014-05-07  9:31             ` David du Colombier
2014-05-07 11:13               ` lucio
2014-05-07 11:30                 ` Charles Forsyth
2014-05-07 14:36                 ` erik quanstrom
2014-05-07 17:51                   ` lucio
2014-05-07 18:22                     ` erik quanstrom
2014-05-08  5:39                       ` lucio
2014-05-07  8:45           ` Charles Forsyth
2014-05-07  9:12             ` erik quanstrom
2014-05-07  9:20               ` Charles Forsyth
2014-05-07  9:21                 ` erik quanstrom
2014-05-07 12:59                 ` Kurt H Maier
2014-05-07 13:36                   ` Charles Forsyth
2014-05-07 14:39                     ` erik quanstrom
2014-05-06 22:09 ` Kurt H Maier
2014-05-07  0:40 ` erik quanstrom [this message]
2014-05-07  1:01   ` Charles Forsyth
2014-05-07  1:12     ` Kurt H Maier
2014-05-07  1:39       ` Charles Forsyth
2014-05-07  1:14 sl
2014-05-07 18:29 sl
2014-05-07 18:48 ` erik quanstrom
2014-05-08  5:56   ` lucio
2014-05-08  8:58     ` cinap_lenrek
2014-05-08 11:20       ` lucio
2014-05-08 12:07         ` erik quanstrom
2014-05-08 12:46           ` lucio
2014-05-08 13:15             ` Charles Forsyth
2014-05-08 13:48               ` Kurt H Maier
2014-05-08 14:07                 ` lucio
2014-05-08 14:04               ` lucio
2014-05-08 14:15                 ` erik quanstrom
2014-05-08 14:51                   ` lucio
2014-05-08 14:56                     ` Charles Forsyth
2014-05-08 15:16                       ` lucio
2014-05-08 10:55     ` erik quanstrom
2014-05-07 18:56 sl
2014-05-07 19:53 ` erik quanstrom
2014-05-07 19:57 sl
2014-05-07 20:06 ` erik quanstrom
2014-05-07 20:11   ` Jacob Todd
2014-05-07 20:19     ` Lyndon Nerenberg
2014-05-08 12:11       ` lucio
2014-05-07 20:56 sl
2014-05-07 21:17 ` Anthony Sorace
2014-05-07 21:33   ` Lyndon Nerenberg
2014-05-08 11:57     ` lucio
2014-05-08 12:03       ` erik quanstrom
2014-05-08 12:39         ` lucio
2014-05-07 21:38 sl
2014-05-07 22:32 ` Charles Forsyth
2014-05-07 22:39   ` Bakul Shah
2014-05-08  1:38   ` Kurt H Maier
2014-05-08  8:41     ` Charles Forsyth
2014-05-08 14:06     ` erik quanstrom
2014-05-08 14:14       ` balaji
2014-05-08 14:20         ` Charles Forsyth
2014-05-07 22:46 ` Anthony Sorace
2014-05-07 23:01 ` Charles Forsyth
2014-05-07 23:51   ` erik quanstrom
2014-05-07 22:36 sl
2014-05-07 23:29 sl
2014-05-07 23:42 ` andrey mirtchovski
2014-05-07 23:37 sl
2014-05-08 13:45 erik quanstrom
2014-05-08 13:55 ` Kurt H Maier
2014-05-08 16:35   ` Jeremy Jackins
2014-05-08 17:16     ` Kurt H Maier
2014-05-08 17:47       ` Jeremy Jackins

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=690893a06bbadd835f847e3f9faf741a@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).