From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"patches@linaro.org" <patches@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] configure: Warn about deprecated hosts
Date: Fri, 17 Mar 2017 11:52:01 +0000 [thread overview]
Message-ID: <CAFEAcA8Sky0cX+7U257AdG=imYYcdqRgL--o=86xCHMY6Kr3zw@mail.gmail.com> (raw)
In-Reply-To: <20170317114953.GF8050@redhat.com>
On 17 March 2017 at 11:49, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Fri, Mar 17, 2017 at 11:08:22AM +0000, Peter Maydell wrote:
>> We plan to drop support in a future QEMU release for host OSes
>> and host architectures for which we have no test machine where
>> we can build and run tests. For the 2.9 release, make configure
>> print a warning if it is run on such a host, so that the user
>> has some warning of the plans and can volunteer to help us
>> maintain the port if they need it to continue to function.
>>
>> This commit flags up as deprecated the CPU architectures:
>> * ia64
>> * sparc
>> * anything which we don't have a TCG port for
>> (and which was presumably using TCI)
>
> This seems to imply that if we remove supported for these architectures,
> then TCI is no longer required either, or would there be other reasons
> to want to keep TCI around, even when all host archs have a TCG port ?
I've never really seen the point in TCI, but others do, which
is why it's in the tree.
>> This list is definitely too all-encompassing, and we should
>> move at least some of the BSDs into "not-deprecated".
>> I'm posting the patch for the moment for code review on the
>> logic and as a placeholder.
>
> FreeBSD is the one where I most frequently see developers engaging across
> the overall virt tools stack (QEMU/libvirt/virt-manager/OpenStack).
> GNU/kFreeBSD has come up a few times in libvirt, and I don't recall seeing
> anyone mentioning the remaining BSDs - though perhaps thats because the
> FreeBSD port fixes are enough to also make other BSDs work.
Yeah. I'm just struggling with setting up a FreeBSD VM so we
can compile test that. Interesting that GNU/kFreeBSD has users.
thanks
-- PMM
next prev parent reply other threads:[~2017-03-17 11:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 11:08 [Qemu-devel] [PATCH] configure: Warn about deprecated hosts Peter Maydell
2017-03-17 11:49 ` Daniel P. Berrange
2017-03-17 11:52 ` Peter Maydell [this message]
2017-03-17 11:56 ` Daniel P. Berrange
2017-03-17 13:10 ` Andrea Bolognani
2017-03-17 13:19 ` Thomas Huth
2017-03-17 13:22 ` Peter Maydell
2017-03-17 13:50 ` Thomas Huth
2017-03-17 13:25 ` Peter Maydell
2017-03-17 23:15 ` Richard Henderson
2017-03-17 12:38 ` Andrew Jones
2017-03-17 15:19 ` Peter Maydell
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='CAFEAcA8Sky0cX+7U257AdG=imYYcdqRgL--o=86xCHMY6Kr3zw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).