From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
aik@ozlabs.ru
Cc: peter.maydell@linaro.org, Marcel Apfelbaum <marcel.a@redhat.com>,
mjt@tls.msk.ru, qemu-devel@nongnu.org, stefanha@redhat.com,
Laszlo Ersek <lersek@redhat.com>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH for-2.0 V3] tests/acpi-test: do not run iasl on big endian machines
Date: Mon, 24 Mar 2014 12:02:14 +0100 [thread overview]
Message-ID: <533010B6.8050609@suse.de> (raw)
In-Reply-To: <20140323094943.GA6989@redhat.com>
Am 23.03.2014 10:49, schrieb Michael S. Tsirkin:
> On Fri, Mar 21, 2014 at 12:16:53AM +0100, Paolo Bonzini wrote:
>> Il 20/03/2014 23:33, Marcel Apfelbaum ha scritto:
>>> I've seen something like that somewhere, but I didn't quite like it.
>>> I was looking for something more elegant as I was *almost* sure
>>> this kind of solution will not pass the reviews :)
>>>
>>> But maybe I'll try this, let's see what happens,
>>
>> If all you're looking for is bigendian (disabling iasl disassembly
>> on bigendian makes sense), your patch v2 is fine.
>>
>> Assembling ASL on bigendian is supported by at least Fedora and
>> Debian (and hence Ubuntu).
>>
>> Paolo
>
>
> At this point I'm confused.
> If iasl compiler is broken, we should detect and fix that.
> It might be ok to just detect endian-ness as a quick work-around.
> BTW configure already has code to detect endian-ness:
> if test "$bigendian" = "yes" ; then
> echo "HOST_WORDS_BIGENDIAN=y" >> $config_host_mak
> fi
Careful, this is about the endianness of the built target binary, which
may be different from the endianness of the build system. However I
would hope the tests will not be executed for cross-builds.
Alexey, you're using cross-builds for ppc, right? Have you ever tested
running make check there?
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-24 11:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 21:14 [Qemu-devel] [PATCH for-2.0 V3] tests/acpi-test: do not run iasl on big endian machines Marcel Apfelbaum
2014-03-20 21:57 ` Paolo Bonzini
2014-03-20 22:00 ` Marcel Apfelbaum
2014-03-20 22:06 ` Marcel Apfelbaum
2014-03-20 22:17 ` Peter Maydell
2014-03-20 22:41 ` Marcel Apfelbaum
2014-03-20 23:03 ` Peter Maydell
2014-03-23 9:52 ` Michael S. Tsirkin
2014-03-23 12:31 ` Peter Maydell
2014-03-23 9:51 ` Michael S. Tsirkin
2014-03-20 22:26 ` Laszlo Ersek
2014-03-20 22:33 ` Marcel Apfelbaum
2014-03-20 22:50 ` Laszlo Ersek
2014-03-20 23:16 ` Paolo Bonzini
2014-03-23 9:49 ` Michael S. Tsirkin
2014-03-23 12:14 ` Peter Maydell
2014-03-23 12:32 ` Marcel Apfelbaum
2014-03-23 12:48 ` Peter Maydell
2014-03-23 13:00 ` Marcel Apfelbaum
2014-03-23 12:51 ` Paolo Bonzini
2014-03-23 13:17 ` Marcel Apfelbaum
2014-03-23 13:58 ` Michael S. Tsirkin
2014-03-24 11:02 ` Andreas Färber [this message]
2014-03-25 3:48 ` Alexey Kardashevskiy
2014-03-23 12:32 ` Marcel Apfelbaum
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=533010B6.8050609@suse.de \
--to=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
/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).