qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: G 3 <programmingkidx@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] More platforms for the wiki
Date: Fri, 11 Nov 2016 13:02:50 +0000	[thread overview]
Message-ID: <20161111130250.GF8930@stefanha-x1.localdomain> (raw)
In-Reply-To: <3B9DDD9A-9789-45AA-AE78-3521B2B094EA@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]

On Fri, Nov 11, 2016 at 12:04:47AM -0500, G 3 wrote:
> http://fossboss.com/2016/08/13/use-qemu-test-operating-systems-distributions/
> 
> On this page I found a huge list of QEMU emulators. I haven't heard of most
> of them, but some of them are not on the platforms page. Do you think we
> should add the missing ones?

A lot of them are 32-bit/64-bit and little-/big-endian variants of an
architecture.

The unique ones I see are:

ARM, Alpha, Cris, i386, lm32, m68k, Microblaze, MIPS, Moxie, OR32, PPC,
SH4, SPARC, Tricore, Unicore32, and xtensa.

Whew!  That's 16 architectures.

Some of the 32- vs 64-bit variants have big differences in instruction
sets and features.  However, people searching for information may not
know when to search for the specific variant versus when to look for the
common architecture.

I think it is simpler to house variants on a single wiki page (i.e.  ARM
for both aarch64 and arm).  Then we can use Mediawiki redirects to also
catch the specific variant names.

But ultimately it's up to the wiki page authors to decide.

> qemu-system-aarch64
> qemu-system-alpha
> qemu-system-arm
> qemu-system-cris
> qemu-system-i386
> qemu-system-lm32
> qemu-system-m68k
> qemu-system-microblaze
> qemu-system-microblazeel
> qemu-system-mips
> qemu-system-mips64
> qemu-system-mips64el
> qemu-system-mipsel
> qemu-system-moxie
> qemu-system-or32
> qemu-system-ppc
> qemu-system-ppc64
> qemu-system-ppc64le
> qemu-system-ppcemb
> qemu-system-sh4
> qemu-system-sh4eb
> qemu-system-sparc
> qemu-system-sparc64
> qemu-system-tricore
> qemu-system-unicore32
> qemu-system-x86_64
> qemu-system-x86_64-spice
> qemu-system-xtensa
> qemu-system-xtensaeb
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2016-11-11 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11  5:04 [Qemu-devel] More platforms for the wiki G 3
2016-11-11 11:02 ` Paolo Bonzini
2016-11-11 13:02 ` Stefan Hajnoczi [this message]
2016-11-11 21:03   ` Max Filippov
2016-11-11 21:09     ` G 3
2016-11-11 15:16 ` Bastian Koppelmann
2016-11-11 15:18   ` G 3
2016-11-11 15:48     ` Bastian Koppelmann
2016-11-11 16:15       ` G 3

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=20161111130250.GF8930@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).