All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Leon Alrae <leon.alrae@imgtec.com>,
	James Hogan <james.hogan@imgtec.com>, vt <vt@sangfor.com.cn>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Question]Support of China loogson processor
Date: Thu, 16 Apr 2015 14:02:01 +0200	[thread overview]
Message-ID: <552FA4B9.4070204@redhat.com> (raw)
In-Reply-To: <552F97FF.4000109@imgtec.com>



On 16/04/2015 13:07, Leon Alrae wrote:
> Since I also haven't had a chance to test Loongson emulation, I thought
> I'd give it a try (TCG only, Loongson-2E cpu and fulong2e machine).
> 
> Good news is that I'm able to get to the login prompt using ancient QEMU
> v1.0, kernel 2.6.33 (with additional patch from
> https://lists.gnu.org/archive/html/qemu-devel/2010-06/msg02566.html) and
> some old debian image I had handy. However, in any newer version
> starting from v1.1.0 of QEMU something goes horribly wrong and it just
> segfaults somewhere inside hw/bonito.c quite early during kernel
> booting.

Where exactly?  If it's related to the memory API conversion, it may be
easy to fix.  I can look at a backtrace (or you can just put the Debian
image somewhere I can grab it).

Paolo

> I haven't looked deeper, but it seems it's not in the best shape...

  reply	other threads:[~2015-04-16 12:02 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
2015-04-16 11:07   ` Leon Alrae
2015-04-16 12:02     ` Paolo Bonzini [this message]
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=552FA4B9.4070204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=james.hogan@imgtec.com \
    --cc=leon.alrae@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.