All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Cc: Richard Henderson <rth@twiddle.net>,
	Peter Maydell <peter.maydell@linaro.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	QEMU Developer <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: Obsolete QEMU host environments
Date: Wed, 15 Mar 2017 11:02:10 +0100	[thread overview]
Message-ID: <bd6016ed-c3a8-8988-b4f8-2cd443874fd0@redhat.com> (raw)
In-Reply-To: <20170315094055.GC7770@redhat.com>

On 15.03.2017 10:40, Daniel P. Berrange wrote:
> On Wed, Mar 15, 2017 at 07:09:55AM +1000, Richard Henderson wrote:
>> On 03/15/2017 03:07 AM, Peter Maydell wrote:
>>> On 14 March 2017 at 17:54, Thomas Huth <thuth@redhat.com> wrote:
>>>> Our ia64 host backend in QEMU (tcg/ia64) is still marked as maintained
>>>> ... so it's maybe not as dead as you think? Or should we rather get rid
>>>> of that soon, too?
>>>
>>> I don't actually mind whether we keep tcg/ia64 or drop it.
>>> But if we keep it then we must have a machine we can test
>>> it on -- that means one I have access to (and which we
>>> can otherwise use for central testing), not just one the
>>> maintainer might happen to have.
>>>
>>> Also, that MAINTAINERS entry was added in 2011, so it's
>>> probably about as out of date as the code :-)
>>
>> Red Hat's last ia64 machine died a few years ago, so I haven't
>> been able to test it for quite some time.
> 
> AFAIK, HP are the only major vendor who still sell new ia64 machines and
> that's high end stuff costing many $$$$$. Even they are pushing people to
> x86_64 unless they need ia64 for legacy reasons. Otherwise ebay and other
> secondhand marketplaces are the only way to get hold of ia64.

Unless Aurelien speaks up and says that it is still maintained, I'd say
we add a big fat "ia is deprecated and going to be removed" warning to
the configure script once we left the freeze state. If nobody then
speaks up within the next two or three releases of QEMU, we remove the
ia64 support from QEMU.

 Thomas

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Cc: Richard Henderson <rth@twiddle.net>,
	Peter Maydell <peter.maydell@linaro.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	QEMU Developer <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Obsolete QEMU host environments
Date: Wed, 15 Mar 2017 11:02:10 +0100	[thread overview]
Message-ID: <bd6016ed-c3a8-8988-b4f8-2cd443874fd0@redhat.com> (raw)
In-Reply-To: <20170315094055.GC7770@redhat.com>

On 15.03.2017 10:40, Daniel P. Berrange wrote:
> On Wed, Mar 15, 2017 at 07:09:55AM +1000, Richard Henderson wrote:
>> On 03/15/2017 03:07 AM, Peter Maydell wrote:
>>> On 14 March 2017 at 17:54, Thomas Huth <thuth@redhat.com> wrote:
>>>> Our ia64 host backend in QEMU (tcg/ia64) is still marked as maintained
>>>> ... so it's maybe not as dead as you think? Or should we rather get rid
>>>> of that soon, too?
>>>
>>> I don't actually mind whether we keep tcg/ia64 or drop it.
>>> But if we keep it then we must have a machine we can test
>>> it on -- that means one I have access to (and which we
>>> can otherwise use for central testing), not just one the
>>> maintainer might happen to have.
>>>
>>> Also, that MAINTAINERS entry was added in 2011, so it's
>>> probably about as out of date as the code :-)
>>
>> Red Hat's last ia64 machine died a few years ago, so I haven't
>> been able to test it for quite some time.
> 
> AFAIK, HP are the only major vendor who still sell new ia64 machines and
> that's high end stuff costing many $$$$$. Even they are pushing people to
> x86_64 unless they need ia64 for legacy reasons. Otherwise ebay and other
> secondhand marketplaces are the only way to get hold of ia64.

Unless Aurelien speaks up and says that it is still maintained, I'd say
we add a big fat "ia is deprecated and going to be removed" warning to
the configure script once we left the freeze state. If nobody then
speaks up within the next two or three releases of QEMU, we remove the
ia64 support from QEMU.

 Thomas

  reply	other threads:[~2017-03-15 10:02 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 20:45 KVM call for 2017-03-14 Juan Quintela
2017-03-12 20:45 ` [Qemu-devel] " Juan Quintela
2017-03-13 10:02 ` Peter Maydell
2017-03-13 12:50   ` Alex Bennée
2017-03-13 14:12   ` Juan Quintela
2017-03-13 14:12     ` [Qemu-devel] " Juan Quintela
2017-03-13 14:17     ` Peter Maydell
2017-03-13 14:17       ` [Qemu-devel] " Peter Maydell
2017-03-14  8:03     ` Stefan Hajnoczi
2017-03-14  8:13   ` Stefan Hajnoczi
2017-03-14  8:37     ` Peter Maydell
2017-03-14  8:59       ` Juan Quintela
2017-03-14  8:59         ` [Qemu-devel] " Juan Quintela
2017-03-14 10:56         ` Peter Maydell
2017-03-14 10:56           ` [Qemu-devel] " Peter Maydell
2017-03-15  8:39           ` Christian Borntraeger
2017-03-15  8:39             ` [Qemu-devel] " Christian Borntraeger
2017-03-15 10:29           ` Greg Kurz
2017-03-15 11:25             ` Laurent Vivier
2017-03-15 11:25               ` Laurent Vivier
2017-03-15 16:35               ` Greg Kurz
2017-03-14 16:01         ` Dr. David Alan Gilbert
2017-03-14 16:20           ` Daniel P. Berrange
2017-03-14 16:54             ` Obsolete QEMU host environments (was: Re: KVM call for 2017-03-14) Thomas Huth
2017-03-14 16:54               ` [Qemu-devel] " Thomas Huth
2017-03-14 17:07               ` Peter Maydell
2017-03-14 17:07                 ` [Qemu-devel] " Peter Maydell
2017-03-14 21:09                 ` Obsolete QEMU host environments Richard Henderson
2017-03-14 21:09                   ` [Qemu-devel] " Richard Henderson
2017-03-15  9:40                   ` Daniel P. Berrange
2017-03-15  9:40                     ` [Qemu-devel] " Daniel P. Berrange
2017-03-15 10:02                     ` Thomas Huth [this message]
2017-03-15 10:02                       ` Thomas Huth
2017-03-15 15:46                   ` Aurelien Jarno
2017-03-15 15:46                     ` [Qemu-devel] " Aurelien Jarno
2017-03-14 17:14             ` [Qemu-devel] KVM call for 2017-03-14 Paolo Bonzini
2017-03-14 17:18           ` Peter Maydell
2017-03-14 17:29             ` Dr. David Alan Gilbert
2017-03-15  8:30               ` Gerd Hoffmann
2017-03-14  9:33       ` Markus Armbruster
2017-03-14  8:53     ` Juan Quintela
2017-03-14  8:53       ` [Qemu-devel] " Juan Quintela
2017-03-14 10:39     ` Peter Maydell
2017-03-14 10:44       ` Paolo Bonzini
2017-03-14  9:24   ` Thomas Huth
2017-03-14 10:13     ` Kevin Wolf
2017-03-14 12:20       ` Markus Armbruster
2017-03-14 12:35         ` Kevin Wolf
2017-03-14 10:32     ` 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=bd6016ed-c3a8-8988-b4f8-2cd443874fd0@redhat.com \
    --to=thuth@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.