qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
  • * Re: [Qemu-devel] Maintainers, please tell us how to boot your machines!
           [not found] <87d0mwatbu.fsf@dusky.pond.sub.org>
           [not found] ` <CAAdtpL6VCiXLbTWyJo4cbCNLjOCPr6KrH8KTqEq1V=CTMYKubQ@mail.gmail.com>
    @ 2019-04-16  2:24 ` Andrey Smirnov
      2019-04-16  2:24   ` Andrey Smirnov
      2019-04-16  9:13 ` KONRAD Frederic
      2019-05-16 20:07 ` Philippe Mathieu-Daudé
      3 siblings, 1 reply; 18+ messages in thread
    From: Andrey Smirnov @ 2019-04-16  2:24 UTC (permalink / raw)
      To: Markus Armbruster
      Cc: QEMU Developers, Cédric Le Goater, Edgar E. Iglesias,
    	Hervé Poussineau, Michael S. Tsirkin,
    	Philippe Mathieu-Daudé,
    	Aleksandar Markovic, Aleksandar Rikalo, Alistair Francis,
    	Alistair Francis, Andrew Baumann, Andrew Jeffery,
    	Andrzej Zaborowski, Anthony Green, Anthony Perard, Antony Pavlov,
    	Artyom Tarasenko, Aurelien Jarno, BALATON Zoltan,
    	Bastian Koppelmann, Beniamino Galvani, Chris Wulff,
    	Christian Borntraeger, Cornelia Huck, David Gibson,
    	David Hildenbrand, Eduardo Habkost, Fabien Chouteau, Guan Xuetao,
    	Halil Pasic, Helge Deller, Igor Mitsyanko, Jan Kiszka,
    	Jean-Christophe Dubois, Jia Liu, Joel Stanley, Magnus Damm,
    	Marcel Apfelbaum, Marek Vasut, Mark Cave-Ayland, Max Filippov,
    	Michael Walle, Palmer Dabbelt, Paolo Bonzini, Paul Burton,
    	Paul Durrant, Peter Chubb, Peter Maydell, Richard Henderson,
    	Rob Herring, Sagar Karandikar, Stafford Horne,
    	Stefano Stabellini, Subbaraya Sundeep, Thomas Huth
    
    On Tue, Mar 12, 2019 at 10:36 AM Markus Armbruster <armbru@redhat.com> wrote:
    >
    > Dear board code maintainers,
    >
    > This is a (rather late) follow-up to the last QEMU summit.  Minutes[*]:
    >
    >  * Deprecating unmaintained features (devices, targets, backends) in QEMU
    >
    >    QEMU has a mechanism to deprecate features but there remains a lot of
    >    old unmaintained code.  Refactoring is hindered by untested legacy
    >    code, so there is a desire to deprecate unmaintained features more
    >    often.
    >
    >    [...]
    >
    >    We should require at least a minimal test for each board; if nobody
    >    cares enough to come up with one, that board should be deprecated.
    >
    >    [...]
    >
    >    Also see the qemu-devel discussion about deprecating code:
    >    https://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg05828.html.
    >
    > That's a link to "Minutes of KVM Forum BoF on deprecating stuff".
    > Quote:
    >
    >  * One obvious class of candidates for removal is machines we don't know
    >    how to boot, or can't boot, say because we lack required firmware
    >    and/or OS.
    >
    >    Of course, "can boot" should be an automated test.  As a first step
    >    towards that, we should at least document how to boot each machine.
    >    We're going to ask machine maintainers to do that.
    >
    > Let's get going on this.
    >
    > I gathered the machine types, mapped them to source files, which I fed
    > to get_maintainer.pl.  Results are appended.  If you're cc'ed,
    > MAINTAINERS fingers you for at least one machine type's source file.
    > Please tell us for all of them how to to a "meaningful" boot test.
    >
    > For now, what's "meaningful" is entirely up to you.  Booting Linux
    > certainly is.
    >
    > Make sure to include a complete QEMU command line.  If your QEMU command
    > line requires resources beyond the QEMU source tree and what we build
    > from it, please detail them, and provide download URLs as far as
    > possible.
    >
    > Goals for this exercise:
    >
    > * Gather information we need to cover more machines in our automated
    >   testing.
    >
    >   Related work:
    >   [PATCH v4 00/19] Acceptance Tests: target architecture support
    >   Message-Id: <20190312121150.8638-1-crosa@redhat.com>
    >   https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg03881.html
    >
    > * Maybe identify a few machines we don't know how to boot anymore.
    >
    > Thanks in advance for your help!
    >
    >
    >
    > Machines with at least one maintainer:
    >
    >
    >     = hw/arm/mcimx7d-sabre.c =
    >     Peter Maydell <peter.maydell@linaro.org> (odd fixer:MCIMX7D SABRE / i...)
    >     Andrey Smirnov <andrew.smirnov@gmail.com> (reviewer:MCIMX7D SABRE / i...)
    >     qemu-arm@nongnu.org (open list:MCIMX7D SABRE / i...)
    >
    
    Sorry I am late to this party. I haven't used i.MX7 emulation in a
    while and things didn't go smoothly out of the box, so I had to create
    a number of fixes (submitted to the ML).
    
    I use Linux kernel built using Buildroot for validation. Buildroot
    should have a default i.MX7 Sabred SD configuration and that should
    probably work. I usually change mine slightly to use compiled-in
    rootfs to simplify storage setup.
    
    In case this is helpful here's a number of commands I use to start my
    test cases:
    
    * PCIe (e1000 ethernet attached), USB (usb stick attached), SD:
    arm-softmmu/qemu-system-arm -smp 2 -m 1024 -machine mcimx7d-sabre
    -nographic -serial mon:stdio -kernel <path to zImage> -dtb <path to
    DTB> -device e1000e,bus="dw-pcie",netdev=lan0 -netdev
    tap,id=lan0,ifname=tap0,script=no,downscript=no -append
    "console=ttymxc0,115200 noinitrd" -usb -drive
    if=none,id=stick,file=<patch to USB stick image>,format=raw -device
    usb-storage,bus=usb-bus.0,drive=stick -drive
    id=sd1,if=sd,format=file,file=<path to SD1> -drive
    id=sd2,if=sd,format=file,file=<path to SD2> -driv
    eid=sd3,if=sd,format=file,file=<path to SD3>
    
    * EHCI USB attached via PCIe with legacy interrupts, Ethernet
    connected to built-in controller:
    arm-softmmu/qemu-system-arm -smp 2 -m 1024 -machine mcimx7d-sabre
    -nographic -serial mon:stdio -kernel <path to zImage> -dtb <path to
    DTB> -device usb-ehci,id=ehci,bus="dw-pcie" -net
    nic,model=imx.fec,netdev=lan0 -netdev
    tap,id=lan0,ifname=tap0,script=no,downscript=no -append
    "console=ttymxc0,115200 noinitrd pci=nomsi" -usb -drive
    if=none,id=stick,file=<path to USB stick image>,format=raw
    
    Also, I don't think anyone would try to do this, but just as a
    warning, building QEMU with --enable-tcg-interpreter doesn't really
    work that well (/init gets SIGKILLed every time), so I'd recommend
    avoiding using that option.
    
    Hopefully this is enough info, but if not, feel free to ask me more questions.
    
    Thanks,
    Andrey Smirnov
    
    ^ permalink raw reply	[flat|nested] 18+ messages in thread
  • * Re: [Qemu-devel] Maintainers, please tell us how to boot your machines!
           [not found] <87d0mwatbu.fsf@dusky.pond.sub.org>
           [not found] ` <CAAdtpL6VCiXLbTWyJo4cbCNLjOCPr6KrH8KTqEq1V=CTMYKubQ@mail.gmail.com>
      2019-04-16  2:24 ` Andrey Smirnov
    @ 2019-04-16  9:13 ` KONRAD Frederic
      2019-04-16  9:13   ` KONRAD Frederic
      2019-05-16 20:07 ` Philippe Mathieu-Daudé
      3 siblings, 1 reply; 18+ messages in thread
    From: KONRAD Frederic @ 2019-04-16  9:13 UTC (permalink / raw)
      To: Markus Armbruster, qemu-devel
      Cc: Paul Burton, Cornelia Huck, Peter Maydell, Sagar Karandikar,
    	Michael S. Tsirkin, Anthony Green, Palmer Dabbelt,
    	Mark Cave-Ayland, Igor Mitsyanko, Max Filippov, Alistair Francis,
    	Edgar E. Iglesias, Guan Xuetao, Peter Chubb, Marek Vasut,
    	Rob Herring, Stefano Stabellini, Jia Liu, Aleksandar Rikalo,
    	Helge Deller, David Hildenbrand, Magnus Damm, Halil Pasic,
    	Christian Borntraeger, Hervé Poussineau, Antony Pavlov,
    	Anthony Perard, Richard Henderson, Artyom Tarasenko,
    	Joel Stanley, Eduardo Habkost, Alistair Francis, Fabien Chouteau,
    	Beniamino Galvani, Paul Durrant, Jan Kiszka,
    	Cédric Le Goater, Stafford Horne, Subbaraya Sundeep,
    	David Gibson, Andrew Jeffery, Bastian Koppelmann, Chris Wulff,
    	Philippe Mathieu-Daudé,
    	Andrew Baumann, Jean-Christophe Dubois, Andrey Smirnov,
    	Michael Walle, Thomas Huth, Aleksandar Markovic, Paolo Bonzini,
    	Aurelien Jarno
    
    
    Le 3/12/19 à 6:36 PM, Markus Armbruster a écrit :
    > Dear board code maintainers,
    
    Hi Markus,
    
    > 
    > This is a (rather late) follow-up to the last QEMU summit.  Minutes[*]:
    > 
    
    [...]
    
    > 
    >      = hw/sparc/leon3.c =
    >      Fabien Chouteau <chouteau@adacore.com> (maintainer:Leon3)
    >      Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> (maintainer:SPARC)
    >      Artyom Tarasenko <atar4qemu@gmail.com> (maintainer:SPARC)
    
    We are still using with this board. I'll try to create a working linux image for
    it and get back to you.
    
    Cheers,
    Fred
    
    ^ permalink raw reply	[flat|nested] 18+ messages in thread
  • * Re: [Qemu-devel] Maintainers, please tell us how to boot your machines!
           [not found] <87d0mwatbu.fsf@dusky.pond.sub.org>
                       ` (2 preceding siblings ...)
      2019-04-16  9:13 ` KONRAD Frederic
    @ 2019-05-16 20:07 ` Philippe Mathieu-Daudé
      2019-05-17 17:42   ` Markus Armbruster
      3 siblings, 1 reply; 18+ messages in thread
    From: Philippe Mathieu-Daudé @ 2019-05-16 20:07 UTC (permalink / raw)
      To: Markus Armbruster, qemu-devel
      Cc: Paul Burton, Chris Wulff, Sagar Karandikar, Michael S. Tsirkin,
    	Andrew Jeffery, Anthony Green, Palmer Dabbelt, Mark Cave-Ayland,
    	Max Filippov, Alistair Francis, Edgar E. Iglesias, Guan Xuetao,
    	Marek Vasut, Rob Herring, Stefano Stabellini, Jia Liu,
    	Peter Maydell, Helge Deller, David Hildenbrand, Magnus Damm,
    	Halil Pasic, Christian Borntraeger, Hervé Poussineau,
    	Antony Pavlov, Anthony Perard, David Gibson, Artyom Tarasenko,
    	Joel Stanley, Eduardo Habkost, Jean-Christophe Dubois,
    	Alistair Francis, Fabien Chouteau, Beniamino Galvani,
    	Paul Durrant, Peter Chubb, Cédric Le Goater, Paolo Bonzini,
    	Stafford Horne, Andrey Smirnov, Richard Henderson,
    	Igor Mitsyanko, Bastian Koppelmann, Cornelia Huck,
    	Philippe Mathieu-Daudé,
    	Andrew Baumann, Subbaraya Sundeep, Aleksandar Rikalo,
    	Michael Walle, Thomas Huth, Aleksandar Markovic, Jan Kiszka,
    	Aurelien Jarno
    
    Hi Markus,
    
    On 3/12/19 6:36 PM, Markus Armbruster wrote:
    > Dear board code maintainers,
    > 
    > This is a (rather late) follow-up to the last QEMU summit.  Minutes[*]:
    > 
    >  * Deprecating unmaintained features (devices, targets, backends) in QEMU
    > 
    >    QEMU has a mechanism to deprecate features but there remains a lot of
    >    old unmaintained code.  Refactoring is hindered by untested legacy
    >    code, so there is a desire to deprecate unmaintained features more
    >    often.
    > 
    >    [...]
    > 
    >    We should require at least a minimal test for each board; if nobody
    >    cares enough to come up with one, that board should be deprecated.
    > 
    >    [...]
    > 
    >    Also see the qemu-devel discussion about deprecating code:
    >    https://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg05828.html.
    > 
    > That's a link to "Minutes of KVM Forum BoF on deprecating stuff".
    > Quote:
    > 
    >  * One obvious class of candidates for removal is machines we don't know
    >    how to boot, or can't boot, say because we lack required firmware
    >    and/or OS.
    > 
    >    Of course, "can boot" should be an automated test.  As a first step
    >    towards that, we should at least document how to boot each machine.
    >    We're going to ask machine maintainers to do that.
    > 
    > Let's get going on this.
    > 
    > I gathered the machine types, mapped them to source files, which I fed
    > to get_maintainer.pl.  Results are appended.  If you're cc'ed,
    > MAINTAINERS fingers you for at least one machine type's source file.
    > Please tell us for all of them how to to a "meaningful" boot test.
    > 
    > For now, what's "meaningful" is entirely up to you.  Booting Linux
    > certainly is.
    > 
    > Make sure to include a complete QEMU command line.  If your QEMU command
    > line requires resources beyond the QEMU source tree and what we build
    > from it, please detail them, and provide download URLs as far as
    > possible.
    > 
    > Goals for this exercise:
    > 
    > * Gather information we need to cover more machines in our automated
    >   testing.
    > 
    >   Related work:
    >   [PATCH v4 00/19] Acceptance Tests: target architecture support
    >   Message-Id: <20190312121150.8638-1-crosa@redhat.com>
    >   https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg03881.html
    > 
    > * Maybe identify a few machines we don't know how to boot anymore.
    > 
    > Thanks in advance for your help!
    
    How do you want to proceed with all the information provided in this
    thread? I think a big table in the wiki collecting the answers is ideal.
    What do you think?
    
    Regards,
    
    Phil.
    
    
    ^ permalink raw reply	[flat|nested] 18+ messages in thread

  • end of thread, other threads:[~2020-01-13 12:54 UTC | newest]
    
    Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
    -- links below jump to the message on this page --
         [not found] <87d0mwatbu.fsf@dusky.pond.sub.org>
         [not found] ` <CAAdtpL6VCiXLbTWyJo4cbCNLjOCPr6KrH8KTqEq1V=CTMYKubQ@mail.gmail.com>
    2019-04-12 11:11   ` [Qemu-devel] Maintainers, please tell us how to boot your machines! Thomas Huth
    2019-04-12 11:11     ` Thomas Huth
    2019-04-12 11:28     ` Philippe Mathieu-Daudé
    2019-04-12 11:28       ` Philippe Mathieu-Daudé
    2019-04-12 12:12       ` Thomas Huth
    2019-04-12 12:12         ` Thomas Huth
    2019-04-12 14:42         ` Thomas Huth
    2019-04-12 14:42           ` Thomas Huth
    2019-04-18  8:16   ` sundeep subbaraya
    2019-04-18  8:16     ` sundeep subbaraya
    2019-04-16  2:24 ` Andrey Smirnov
    2019-04-16  2:24   ` Andrey Smirnov
    2019-04-16  9:13 ` KONRAD Frederic
    2019-04-16  9:13   ` KONRAD Frederic
    2019-05-16 20:07 ` Philippe Mathieu-Daudé
    2019-05-17 17:42   ` Markus Armbruster
    2019-12-22 12:03     ` Philippe Mathieu-Daudé
    2020-01-13 12:52       ` Markus Armbruster
    

    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).