qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Peter Tribble <peter.tribble@gmail.com>
Cc: Kamil Rytarowski <n54@gmx.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SunOS support
Date: Fri, 22 Sep 2017 17:51:17 +0200	[thread overview]
Message-ID: <e9861b1a-296c-6233-4e47-6af3f8dc37e7@redhat.com> (raw)
In-Reply-To: <CAFEAcA_UDk4cwtq4G_XArGCH4LC3hLUnmVHO28RJnm+7=YD_BA@mail.gmail.com>

On 22/09/2017 14:05, Peter Maydell wrote:
> On 20 September 2017 at 19:50, Peter Tribble <peter.tribble@gmail.com> wrote:
>> To introduce myself: I'm a member of the illumos community (the successor
>> to OpenSolaris, to those unfamiliar with us), and I maintain my own illumos
>> distribution.
>>
>> Having seen the scary 'SUPPORT FOR THIS HOST OS WILL GO AWAY'
>> message, I'm reaching out to see what needs to be done so that support for
>> SunOS (not just illumos, I include Oracle's Solaris in the same family)
>> needs to be kept and, where possible, enhanced.
>>
>> I'm willing to act as a contact in this effort, and can work with others in
>> the illumos community to see if there are other resources we can bring to bear.
> 
> Hi; thanks for getting in touch with us. Kamil Rytarowski (who I've
> cc'd) is also interested in keeping Solaris-variant support working.
> 
> Essentially what we need as upstream is:
>  * access to a machine which we can use for our continuous
>    integration build testing, so we don't break compile
>    support for the platform. This is ideally a machine that
>    somebody else admins and we just use (because we don't
>    want to become solaris/illumos admins ;-)), but failing
>    that, instructions on how to get a VM running under
>    KVM on Linux would also be OK (that's how we've ended
>    up handling the BSDs)

I would even reverse the order since now we're handling the BSDs using
the VM test infrastructure.  Let's say having both would be best.

Paolo

>  * somebody to look at the places where 'make && make check'
>    currently fails and submit upstream patches for them. Kamil
>    has been doing a great job here but would probably
>    appreciate extra help :-)
>  * somebody who's willing to be listed in our MAINTAINERS file
>    as maintaining the port, so we can ask them questions if/when
>    any platform-specific issues come up in future
> 
> Overall we're happy to continue to support hosts that people
> are still using -- we just want to avoid blindly maintaining
> code for platforms we can't test and where we don't have
> any idea if anybody's even using it (for instance we just
> dropped the support for AIX and for Itanium CPUs...)
> 
> thanks
> -- PMM
> 

  reply	other threads:[~2017-09-22 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 18:50 [Qemu-devel] SunOS support Peter Tribble
2017-09-22 12:05 ` Peter Maydell
2017-09-22 15:51   ` Paolo Bonzini [this message]
2017-09-22 16:10     ` Peter Maydell
2017-09-22 16:37       ` Peter Tribble
2017-09-26 15:12   ` Kamil Rytarowski

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=e9861b1a-296c-6233-4e47-6af3f8dc37e7@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=n54@gmx.com \
    --cc=peter.maydell@linaro.org \
    --cc=peter.tribble@gmail.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).