From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: arikalo@wavecomp.com, ehabkost@redhat.com, qemu-devel@nongnu.org,
aurelien@aurel32.net, crosa@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] tests/acceptance: Handle ppc64le host arch correctly
Date: Fri, 14 Jun 2019 07:55:53 +0200 [thread overview]
Message-ID: <b1f9e994-debe-8de0-d032-9be4400d2cdd@redhat.com> (raw)
In-Reply-To: <20190614015329.GE11158@umbus.fritz.box>
[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]
On 6/14/19 3:53 AM, David Gibson wrote:
> On Fri, Jun 14, 2019 at 11:40:56AM +1000, David Gibson wrote:
>> On Thu, Jun 13, 2019 at 11:01:19AM +0200, Philippe Mathieu-Daudé wrote:
>>> On 6/13/19 8:07 AM, David Gibson wrote:
>>>> ppc64 and ppc64le are different archs from the host kernel point of view
>>>> and are advertised as such in uname. But these cover the same set of CPUs,
>>>> just in different endianness modes. qemu-system-ppc64 handles both modes,
>>>> so make sure we select the correct binary when running on ppc64le host
>>>> architecture.
>>>>
>>>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>>>> ---
>>>> tests/acceptance/avocado_qemu/__init__.py | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/tests/acceptance/avocado_qemu/__init__.py b/tests/acceptance/avocado_qemu/__init__.py
>>>> index 2b236a1cf0..0ba9c536f4 100644
>>>> --- a/tests/acceptance/avocado_qemu/__init__.py
>>>> +++ b/tests/acceptance/avocado_qemu/__init__.py
>>>> @@ -39,6 +39,8 @@ def pick_default_qemu_bin(arch=None):
>>>> """
>>>> if arch is None:
>>>> arch = os.uname()[4]
>>>> + if arch == 'ppc64le':
>>>> + arch = 'ppc64'
>>>
>>> I prefer the generic patch from Cleber:
>>> https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg03418.html
>>> (I guess remember another version with a json file)
>>
>> I hadn't seen that, that does indeed look better.
>
> Hrm. Well, it is better but it's been outstanding for like 8 months.
> I'd just like to get this working on a ppc host in the near future.
True :S I wanted you to know Cleber was working on this, but I don't
have any problem to get your fix merged and Cleber work added on top of
it, so:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-14 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 6:07 [Qemu-devel] [PATCH 0/3] Some fixes for make check-acceptance on a POWER host David Gibson
2019-06-13 6:07 ` [Qemu-devel] [PATCH 1/3] tests/acceptance: Specify arch for QueryCPUModelExpansion David Gibson
2019-06-19 17:24 ` Wainer dos Santos Moschetta
2019-06-13 6:07 ` [Qemu-devel] [PATCH 2/3] tests/acceptance: Handle ppc64le host arch correctly David Gibson
2019-06-13 9:01 ` Philippe Mathieu-Daudé
2019-06-14 1:40 ` David Gibson
2019-06-14 1:53 ` David Gibson
2019-06-14 5:55 ` Philippe Mathieu-Daudé [this message]
2019-06-13 6:07 ` [Qemu-devel] [PATCH 3/3] tests/acceptance: Increase timeout for LinuxSSH test David Gibson
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=b1f9e994-debe-8de0-d032-9be4400d2cdd@redhat.com \
--to=philmd@redhat.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--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).