qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PULL 0/8] Linux user for 2.12 patches
Date: Tue, 20 Feb 2018 10:13:29 +0100	[thread overview]
Message-ID: <3d677b9c-d3aa-d34f-d6fc-48625bd1f77a@vivier.eu> (raw)
In-Reply-To: <CAFEAcA-W+xQMov2=WHPYwh_EVFiaW+8D+0VWB2T6kJ6Bo_xLFw@mail.gmail.com>

Le 19/02/2018 à 20:50, Peter Maydell a écrit :
> On 19 February 2018 at 17:10, Laurent Vivier <laurent@vivier.eu> wrote:
>> The following changes since commit f0fa81767555fe2c4b5f8c9e0725a80eac1d7f56:
>>
>>   cuda.h: Fix multiple typedef (2018-02-16 18:38:21 +0000)
>>
>> are available in the Git repository at:
>>
>>   git://github.com/vivier/qemu.git tags/linux-user-for-2.12-pull-request
>>
>> for you to fetch changes up to f352a021329f73d0219018cdfb39369687e8cadd:
>>
>>   linux-user: MIPS set cpu to r6 CPU if binary is R6 (2018-02-18 18:52:32 +0100)
>>
>> ----------------------------------------------------------------
>>
>> ----------------------------------------------------------------
> 
> Hi. This breaks one of my linux-user smoke tests:
> 
> /home/petmay01/linaro/qemu-for-merges/build/all-linux-static/sparc32plus-linux-user/qemu-sparc32plus
> -L ./gnemul/qemu-sparc sparc/ls -l dummyfile
> unable to find CPU model 'Fujitsu MB86904'
> 
> This is because the include path for linux-user picks the
> guest-architecture subdirectory for the TARGET_ABI_DIR,
> which for sparc32plus is "sparc", but the set of CPUs compiled
> in depends on the TARGET_ARCH, which is "sparc64", and
> sparc64 doesn't include that 32-bit Fujitsu CPU.
> The linux-user/sparc/target_elf.h needs to have code to handle
> both the pure-32-bit and 32-bit-ABI-on-64-bit-CPU cases,
> the same way that linux-user/ppc/target_elf.h does.

Thank you Peter,

I'm going to remove the 4 last patches from the pull request and resend it.

Thanks,
Laurent

      reply	other threads:[~2018-02-20  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 17:10 [Qemu-devel] [PULL 0/8] Linux user for 2.12 patches Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 1/8] linux-user: Implement ioctl cmd TIOCGPTPEER Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 2/8] linux-user: Fix register used for 6th and 7th syscall argument on aarch64 Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 3/8] linux-user: Fix sched_getaffinity mask size Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 4/8] linux-user: Remove THREAD macro Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 5/8] linux-user: Move CPU type name selection to a function Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 6/8] linux-user: introduce functions to detect CPU type Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 7/8] linux-user, m68k: select CPU according to ELF header values Laurent Vivier
2018-02-19 17:10 ` [Qemu-devel] [PULL 8/8] linux-user: MIPS set cpu to r6 CPU if binary is R6 Laurent Vivier
2018-02-19 19:50 ` [Qemu-devel] [PULL 0/8] Linux user for 2.12 patches Peter Maydell
2018-02-20  9:13   ` Laurent Vivier [this message]

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=3d677b9c-d3aa-d34f-d6fc-48625bd1f77a@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).