qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>,
	Thomas Huth <thuth@redhat.com>
Cc: "berrange@redhat.com" <berrange@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [QUESTION] SDL 1.2 support
Date: Mon, 29 Jul 2019 12:36:44 +0200	[thread overview]
Message-ID: <516690e2-fe70-0ff5-cf5d-c087dffb2113@redhat.com> (raw)
In-Reply-To: <fe175e72-48f3-1a20-f9f0-34fbbadcf4a4@redhat.com>

Hi Aleksandar,

On 7/18/19 8:20 AM, Philippe Mathieu-Daudé wrote:
> On 7/16/19 8:20 PM, Philippe Mathieu-Daudé wrote:
>> Hi Aleksandar,
>>
>> On 7/16/19 7:09 PM, Aleksandar Markovic wrote:
>>> On Tue, Jul 16, 2019 at 1:54 PM Thomas Huth <thuth@redhat.com> wrote:
>>>>
>>>> On 16/07/2019 13.17, Aleksandar Markovic wrote:
>>>>> Hello, Gerd, Daniel, and others involved.
>>>>>
>>>>> I have multiple reports from end users that say that transition from
>>>>> SDL 1.2 to SDL 2.0 was difficult, or even impossible for their hosts.
>>>>> In that light, they don't appreciate removing SDL 1.2 support from
>>>>> QEMU. The most notable example is Ubutnu 16.04, where it looks there
>>>>> is no way of installing SDL 2.0 that does not involve complete OS
>>>>> upgrade, which, for various reasons, many are not willing to do.
>>>>
>>>> What's the problem here? According to
>>>> https://packages.ubuntu.com/xenial/libsdl2-2.0-0 the library should be
>>>> available there.
>>>>
>>>
>>> Yes, we, as developers, are good at upgrading, we like flexibility in
>>> our development systems, and naturally want to try latest and greatest
>>> tools and libraries.
>>>
>>> However, in QA / build / test environments, the things seem to look
>>> different. Their main concern is stability and repeatibility of their
>>> systems. They don't like updates and upgrades. If a new of library
>>> is available for an OS, this does not mean it will be installed, or it
>>> will be desired to be installed.
>>>
>>> It appears that Ubuntu 16.04 came originally with SDL 1.2, and
>>> SDL 2.0 was made available later on.
>>
>> I am a bit confused, I checked the older Xenial image I can find is a
>> pre-release:
>>
>> 16.04.20151218.1-xenial-baseline
>>
[...]
> $ make
> [...]
>   GEN     util/trace.c
>         CHK version_gen.h
>          LEX convert-dtsv0-lexer.lex.c
> make[1]: flex: Command not found
>          BISON dtc-parser.tab.c
> make[1]: bison: Command not found
>          LEX dtc-lexer.lex.c
> make[1]: flex: Command not found
>   AR      libcapstone.a
> ar: creating /tmp/qemu-4.1.0-rc0/capstone/libcapstone.a
> [...]
>   CC      mipsel-softmmu/trace/generated-helpers.o
>   LINK    mipsel-softmmu/qemu-system-mipsel
> [...]
>   CC      mips64el-softmmu/target/mips/cp0_timer.o
>   GEN     trace/generated-helpers.c
>   CC      mips64el-softmmu/trace/control-target.o
>   CC      mips64el-softmmu/trace/generated-helpers.o
>   LINK    mips64el-softmmu/qemu-system-mips64el
> [...]
> 
> $ wget
> https://mipsdistros.mips.com/LinuxDistro/nanomips/kernels/v4.15.18-432-gb2eb9a8b07a1-20180627102142/generic_nano32r6el_page16k_up.xz
> 
> $ unxz generic_nano32r6el_page16k_up.xz
> 
> $ ./mipsel-softmmu/qemu-system-mipsel -M malta -cpu I7200 -kernel
> generic_nano32r6el_page16k_up -append console=ttyS0 -nographic
> [    0.000000] Linux version 4.15.18 (emubuild@mipscs567) (gcc version
> 6.3.0 (Codescape GNU Tools 2018.04-02 for nanoMIPS Linux)) #1 Wed Jun 27
> 11:13:09 PDT 2018
> [    0.000000] GCRs appear to have been moved (expected them at 0x1fbf8000)!
> [    0.000000] GCRs appear to have been moved (expected them at 0x1fbf8000)!
> [    0.000000] CPU0 revision is: 00010000 (MIPS GENERIC QEMU)
> [    0.000000] MIPS: machine is mti,malta
> [    0.000000] Determined physical RAM map:
> [    0.000000]  memory: 08000000 @ 00000000 (usable)
> [    0.000000] earlycon: ns16550a0 at I/O port 0x3f8 (options '38400n8')
> [...]
> 
> $ make check-tcg
> [...]
>   BUILD   TCG tests for mips-softmmu
>   BUILD   mips guest-tests SKIPPED
>   RUN     TCG tests for mips-softmmu
>   RUN     tests for mips SKIPPED
>   BUILD   TCG tests for mips64-softmmu
>   BUILD   mips64 guest-tests SKIPPED
>   RUN     TCG tests for mips64-softmmu
>   RUN     tests for mips64 SKIPPED
>   BUILD   TCG tests for mips64el-softmmu
>   BUILD   mips64el guest-tests SKIPPED
>   RUN     TCG tests for mips64el-softmmu
>   RUN     tests for mips64el SKIPPED
>   BUILD   TCG tests for mipsel-softmmu
>   BUILD   mipsel guest-tests SKIPPED
>   RUN     TCG tests for mipsel-softmmu
>   RUN     tests for mipsel SKIPPED
> [...]
>   BUILD   x86_64 guest-tests with cc
>   RUN     tests for x86_64
>   TEST    test-mmap (default) on x86_64
>   TEST    sha1 on x86_64
>   TEST    linux-test on x86_64
>   TEST    testthread on x86_64
>   TEST    test-x86_64 on x86_64
>   TEST    test-mmap (4096 byte pages) on x86_64
> [...]
> $
> 
> Ah, cross-target tests are skipped because I don't have Docker for
> cross-building tests.
> 
> Let's see how you use them:
> 
> $ cat tests/tcg/mips/user/ase/msa/README
> The tests in subdirectories of this directory are supposed to be
> compiled for
> mips64el MSA-enabled CPU (I6400, I6500), using an appropriate MIPS
> toolchain.
> For example:
> 
> /opt/img/bin/mips-img-linux-gnu-gcc <source file>                  \
> -EL -static -mabi=64 -march=mips64r6 -mmsa  -o <executable file>
> 
> They are to be executed using QEMU user mode, using command line:
> 
> mips64el-linux-user/qemu-mips64el -cpu I6400 <executable file>
> [...]
> 
> Googling I find this link:
> https://www.mips.com/develop/tools/codescape-mips-sdk/
> 
> The following host platforms are recommended:
>  Windows 10 (64-bit)
>  Linux: Ubuntu 16.04 (64-bit) and CentOS 7 (64-bit)
> 
> Offline Installer
> These are ~ 3Gbyte and include all components in one installer file.
> 
> OMG I'm not sure I want to continue with this...
> 
> Download in progress.
> 
> I already spent 2h on this today, I have to continue other tasks
> meanwhile, I might continue later.

I spent 1 more hour installing the CodeScape MIPS SDK, even trying to
install it in a Docker image to have it handy or use it in some CI.
However I reached the end of the spare time I could spend trying to
help, and nobody from the community is complaining except your customer.

Since 11 days passed and you haven't replied to my extensive testing, I
am assuming you could figure out how to help your customer with the
other answers to this thread.

Regards,

Phil.


  reply	other threads:[~2019-07-29 10:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 11:17 [Qemu-devel] [QUESTION] SDL 1.2 support Aleksandar Markovic
2019-07-16 11:41 ` Peter Maydell
2019-07-16 17:48   ` Aleksandar Markovic
2019-07-16 18:30     ` Peter Maydell
2019-07-16 11:50 ` Daniel P. Berrangé
2019-07-16 11:54 ` Thomas Huth
2019-07-16 17:09   ` Aleksandar Markovic
2019-07-16 17:44     ` Daniel P. Berrangé
2019-07-16 18:06       ` Aleksandar Markovic
2019-07-16 18:16         ` Daniel P. Berrangé
2019-07-17 18:34       ` Aleksandar Markovic
2019-07-17 18:57         ` Eric Blake
2019-07-17 19:20           ` Aleksandar Markovic
2019-07-17 19:57             ` Eric Blake
2019-07-16 18:20     ` Philippe Mathieu-Daudé
2019-07-18  6:20       ` Philippe Mathieu-Daudé
2019-07-29 10:36         ` Philippe Mathieu-Daudé [this message]
2019-07-29 11:27           ` Aleksandar Markovic

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=516690e2-fe70-0ff5-cf5d-c087dffb2113@redhat.com \
    --to=philmd@redhat.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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).