From: James Hogan <james.hogan@imgtec.com>
To: vt <vt@sangfor.com.cn>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Question]Support of China loogson processor
Date: Wed, 15 Apr 2015 10:35:49 +0100 [thread overview]
Message-ID: <552E30F5.2020207@imgtec.com> (raw)
In-Reply-To: <201504131929543844171@sangfor.com.cn>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On 13/04/15 12:29, vt wrote:
> Hi, guys
>
> I saw the architecture code about mips in the qemu and kvm modules, so it is no doubt that mips cpu can be supported.
> But I wonder if anyone have used qemu/kvm virtualization with China loongson processor (MIPS architecture) without modification of qemu/kvm code.
> All the infomation I have searched in the Internet can't answer my question.
>
> If anyone have done that before, let me know it will not be a dead end.
>
> Thanks
> Sangfor VT
I haven't attempted it on Loongson yet, but it'd be interesting to see
whether it works. You'd still have to emulate a Malta guest at the
moment. Getting it to work on the Ingenic XBurst cores required a little
effort in the kernel due to slight incompatibilities with the MIPS32r2
spec, so its possible there'll be problems with Loongson too.
I presume Loongson may use highmem, if so you'll want to disable it. I
still need to get those patches sorted out.
Let us know how it goes or if you hit problems!
Cheers
James
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-15 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 11:29 [Qemu-devel] [Question]Support of China loogson processor vt
2015-04-15 1:08 ` Rob Landley
2015-04-15 3:53 ` vt
2015-04-15 9:19 ` Andreas Färber
2015-04-15 9:35 ` James Hogan [this message]
2015-04-16 11:07 ` Leon Alrae
2015-04-16 12:02 ` Paolo Bonzini
2015-04-16 15:05 ` Leon Alrae
2015-04-16 15:17 ` Paolo Bonzini
2015-04-16 19:25 ` Leon Alrae
2015-04-16 19:40 ` Paolo Bonzini
2015-04-16 22:00 ` Peter Maydell
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=552E30F5.2020207@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=qemu-devel@nongnu.org \
--cc=vt@sangfor.com.cn \
/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.