From: Utkarsh Sopan <utkarsh.sopan@coe.dce.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Adding support for MIPS64 as host
Date: Wed, 3 Feb 2010 22:23:24 +0530 [thread overview]
Message-ID: <79fd481e1002030853n4e376e91sca7234fdea3d05d3@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Hi,
I am trying to add support for MIPS 64 as Host machine as my academic
project.
I am new to QEMU.
Problem is I dont have a MIPS 64 machine to test on.
Please suggest whether or not I can use a nested QEMU emulator to test the
same.
i.e. running my version on top of a simulated MIPS64 machine.
Is it possible to do so?
[-- Attachment #2: Type: text/html, Size: 367 bytes --]
next reply other threads:[~2010-02-03 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:53 Utkarsh Sopan [this message]
2010-02-03 16:59 ` [Qemu-devel] Adding support for MIPS64 as host Laurent Desnogues
2010-02-04 17:26 ` Utkarsh Sopan
2010-02-04 17:30 ` Laurent Desnogues
2010-02-05 14:46 ` pinery
2010-02-05 9:22 ` Arnaud Patard
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=79fd481e1002030853n4e376e91sca7234fdea3d05d3@mail.gmail.com \
--to=utkarsh.sopan@coe.dce.edu \
--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).