qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] Re: arm, mips and mipsel broken
Date: Wed, 11 Nov 2009 20:08:48 +0200	[thread overview]
Message-ID: <f43fc5580911111008k282a7c9es5f067fdf453a3b8b@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580911110947n1a5a3148y4453c0aadb4a81e7@mail.gmail.com>

On Wed, Nov 11, 2009 at 7:47 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Wed, Nov 11, 2009 at 1:54 AM, Juan Quintela <quintela@trasno.org> wrote:
>> Blue Swirl <blauwirbel@gmail.com> wrote:
>>> On Tue, Nov 10, 2009 at 10:50 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>>>> Please note that at least qemu-system-arm, qemu-system-mips and
>>>> qemu-system-mipsel are broken by this commit:
>>>
>>> Given that none of the devices touched by the commit should be used by
>>> these targets, the breakage comes from just the single new call to
>>> qemu_system_reset in vl.c. This means that the reset functions for
>>> those boards and devices must be awfully buggy.
>>>
>>> I think the easiest solution is to surround the call by
>>> #if defined(TARGET_I386) || defined(TARGET_PPC) || defined(TARGET_SPARC)
>>> #endif
>>> until the devices have been fixed.
>>
>> That call also breaks loadvm from the command line on x86_64.
>> If I revert the rest of the patch except that line, I still get breakage
>> on rtl8139.
>
> Sigh. I'll leave only Sparc for now. Sorry for the trouble.
>

In fact it's easier to revert all commits and commit later one
architecture at a time.

  reply	other threads:[~2009-11-11 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 20:50 [Qemu-devel] arm, mips and mipsel broken Aurelien Jarno
2009-11-10 21:19 ` Blue Swirl
2009-11-10 21:35   ` Aurelien Jarno
2009-11-11 18:28     ` Paul Brook
2009-11-11 21:02       ` Blue Swirl
2009-11-11 21:59         ` Paul Brook
     [not found]   ` <m3r5s6ndg2.fsf@neno.mitica>
2009-11-11 17:47     ` [Qemu-devel] " Blue Swirl
2009-11-11 18:08       ` Blue Swirl [this message]
2009-11-11 18:57   ` [Qemu-devel] " Glauber Costa
2009-11-11 21:00     ` Blue Swirl
2009-11-12 17:34 ` Stefan Weil

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=f43fc5580911111008k282a7c9es5f067fdf453a3b8b@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@trasno.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).