All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Andre Przywara <andre.przywara@arm.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>,
	kvm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>,
	"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" 
	<linux-ide@vger.kernel.org>, Will Deacon <will@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	soc@kernel.org, Joerg Roedel <joro@8bytes.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	devicetree@vger.kernel.org, Jon Loeliger <jdl@jdl.com>,
	"open list:THERMAL" <linux-pm@vger.kernel.org>,
	Eric Auger <eric.auger@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Tony Luck <tony.luck@intel.com>, Alexander Graf <graf@amazon.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-edac <linux-edac@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	Matthias Brugger <mbrugger@suse.com>,
	Stephen Boyd <sboyd@kernel.org>, netdev <netdev@vger.kernel.org>,
	Cornelia Huck <cohuck@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux IOMMU <iommu@lists.linux-foundation.org>,
	Robert Richter <rrichter@marvell.com>,
	James Morse <james.morse@arm.com>, Borislav Petkov <bp@alien8.de>,
	Robin Murphy <robin.murphy@arm.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/11] Removing Calxeda platform support
Date: Tue, 18 Feb 2020 10:51:17 -0800	[thread overview]
Message-ID: <f2b15018-2b88-01b8-14f1-a6c326b10b58@gmail.com> (raw)
In-Reply-To: <CAL_JsqJpDLn5Zr2UHno1TeReqrwZ-HAAfd78AouigGi4sAQuOw@mail.gmail.com>

On 2/18/20 10:40 AM, Rob Herring wrote:
> On Tue, Feb 18, 2020 at 12:14 PM Andre Przywara <andre.przywara@arm.com> wrote:
>>
>> On Tue, 18 Feb 2020 11:13:10 -0600
>> Rob Herring <robh@kernel.org> wrote:
>>
>> Hi,
>>
>>> Calxeda has been defunct for 6 years now. Use of Calxeda servers carried
>>> on for some time afterwards primarily as distro builders for 32-bit ARM.
>>> AFAIK, those systems have been retired in favor of 32-bit VMs on 64-bit
>>> hosts.
>>>
>>> The other use of Calxeda Midway I'm aware of was testing 32-bit ARM KVM
>>> support as there are few or no other systems with enough RAM and LPAE. Now
>>> 32-bit KVM host support is getting removed[1].
>>>
>>> While it's not much maintenance to support, I don't care to convert the
>>> Calxeda DT bindings to schema nor fix any resulting errors in the dts files
>>> (which already don't exactly match what's shipping in firmware).
>>
>> While every kernel maintainer seems always happy to take patches with a negative diffstat, I wonder if this is really justification enough to remove a perfectly working platform. I don't really know about any active users, but experience tells that some platforms really are used for quite a long time, even if they are somewhat obscure. N900 or Netwinder, anyone?
>>
>> So to not give the impression that actually *everyone* (from that small subset of people actively reading the kernel list) is happy with that, I think that having support for at least Midway would be useful. On the one hand it's a decent LPAE platform (with memory actually exceeding 4GB), and on the other hand it's something with capable I/O (SATA) and networking, so one can actually stress test the system. Which is the reason I was using that for KVM testing, but even with that probably going away now there remain still some use cases, and be it for general ARM(32) testing.
> 
> Does LPAE with more than 4GB actually need to work if there's not
> another platform out there?

There are ARCH_BRCMSTB platforms that are 32-bit only and have 6GB of
DRAM populated, and those continue to work just fine, though there is no
known use for KVM AFAICT.
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Andre Przywara <andre.przywara@arm.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>,
	kvm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:LIBATA SUBSYSTEM \(Serial and Parallel ATA drivers\)"
	<linux-ide@vger.kernel.org>, Will Deacon <will@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	devicetree@vger.kernel.org, Jon Loeliger <jdl@jdl.com>,
	"open list:THERMAL" <linux-pm@vger.kernel.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Alexander Graf <graf@amazon.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	linux-edac <linux-edac@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>, Tony Luck <tony.luck@intel.com>,
	Stephen Boyd <sboyd@kernel.org>, netdev <netdev@vger.kernel.org>,
	Cornelia Huck <cohuck@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	soc@kernel.org, Linux IOMMU <iommu@lists.linux-foundation.org>,
	Robert Richter <rrichter@marvell.com>,
	James Morse <james.morse@arm.com>, Borislav Petkov <bp@alien8.de>,
	Robin Murphy <robin.murphy@arm.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/11] Removing Calxeda platform support
Date: Tue, 18 Feb 2020 10:51:17 -0800	[thread overview]
Message-ID: <f2b15018-2b88-01b8-14f1-a6c326b10b58@gmail.com> (raw)
In-Reply-To: <CAL_JsqJpDLn5Zr2UHno1TeReqrwZ-HAAfd78AouigGi4sAQuOw@mail.gmail.com>

On 2/18/20 10:40 AM, Rob Herring wrote:
> On Tue, Feb 18, 2020 at 12:14 PM Andre Przywara <andre.przywara@arm.com> wrote:
>>
>> On Tue, 18 Feb 2020 11:13:10 -0600
>> Rob Herring <robh@kernel.org> wrote:
>>
>> Hi,
>>
>>> Calxeda has been defunct for 6 years now. Use of Calxeda servers carried
>>> on for some time afterwards primarily as distro builders for 32-bit ARM.
>>> AFAIK, those systems have been retired in favor of 32-bit VMs on 64-bit
>>> hosts.
>>>
>>> The other use of Calxeda Midway I'm aware of was testing 32-bit ARM KVM
>>> support as there are few or no other systems with enough RAM and LPAE. Now
>>> 32-bit KVM host support is getting removed[1].
>>>
>>> While it's not much maintenance to support, I don't care to convert the
>>> Calxeda DT bindings to schema nor fix any resulting errors in the dts files
>>> (which already don't exactly match what's shipping in firmware).
>>
>> While every kernel maintainer seems always happy to take patches with a negative diffstat, I wonder if this is really justification enough to remove a perfectly working platform. I don't really know about any active users, but experience tells that some platforms really are used for quite a long time, even if they are somewhat obscure. N900 or Netwinder, anyone?
>>
>> So to not give the impression that actually *everyone* (from that small subset of people actively reading the kernel list) is happy with that, I think that having support for at least Midway would be useful. On the one hand it's a decent LPAE platform (with memory actually exceeding 4GB), and on the other hand it's something with capable I/O (SATA) and networking, so one can actually stress test the system. Which is the reason I was using that for KVM testing, but even with that probably going away now there remain still some use cases, and be it for general ARM(32) testing.
> 
> Does LPAE with more than 4GB actually need to work if there's not
> another platform out there?

There are ARCH_BRCMSTB platforms that are 32-bit only and have 6GB of
DRAM populated, and those continue to work just fine, though there is no
known use for KVM AFAICT.
-- 
Florian
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Andre Przywara <andre.przywara@arm.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>,
	kvm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:LIBATA SUBSYSTEM \(Serial and Parallel ATA drivers\)"
	<linux-ide@vger.kernel.org>, Will Deacon <will@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	Joerg Roedel <joro@8bytes.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	devicetree@vger.kernel.org, Jon Loeliger <jdl@jdl.com>,
	"open list:THERMAL" <linux-pm@vger.kernel.org>,
	Eric Auger <eric.auger@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Matthias Brugger <mbrugger@suse.com>,
	Alexander Graf <graf@amazon.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	linux-edac <linux-edac@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>, Tony Luck <tony.luck@intel.com>,
	Stephen Boyd <sboyd@kernel.org>, netdev <netdev@vger.kernel.org>,
	Cornelia Huck <cohuck@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	soc@kernel.org, Linux IOMMU <iommu@lists.linux-foundation.org>,
	Robert Richter <rrichter@marvell.com>,
	James Morse <james.morse@arm.com>, Borislav Petkov <bp@alien8.de>,
	Robin Murphy <robin.murphy@arm.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/11] Removing Calxeda platform support
Date: Tue, 18 Feb 2020 10:51:17 -0800	[thread overview]
Message-ID: <f2b15018-2b88-01b8-14f1-a6c326b10b58@gmail.com> (raw)
In-Reply-To: <CAL_JsqJpDLn5Zr2UHno1TeReqrwZ-HAAfd78AouigGi4sAQuOw@mail.gmail.com>

On 2/18/20 10:40 AM, Rob Herring wrote:
> On Tue, Feb 18, 2020 at 12:14 PM Andre Przywara <andre.przywara@arm.com> wrote:
>>
>> On Tue, 18 Feb 2020 11:13:10 -0600
>> Rob Herring <robh@kernel.org> wrote:
>>
>> Hi,
>>
>>> Calxeda has been defunct for 6 years now. Use of Calxeda servers carried
>>> on for some time afterwards primarily as distro builders for 32-bit ARM.
>>> AFAIK, those systems have been retired in favor of 32-bit VMs on 64-bit
>>> hosts.
>>>
>>> The other use of Calxeda Midway I'm aware of was testing 32-bit ARM KVM
>>> support as there are few or no other systems with enough RAM and LPAE. Now
>>> 32-bit KVM host support is getting removed[1].
>>>
>>> While it's not much maintenance to support, I don't care to convert the
>>> Calxeda DT bindings to schema nor fix any resulting errors in the dts files
>>> (which already don't exactly match what's shipping in firmware).
>>
>> While every kernel maintainer seems always happy to take patches with a negative diffstat, I wonder if this is really justification enough to remove a perfectly working platform. I don't really know about any active users, but experience tells that some platforms really are used for quite a long time, even if they are somewhat obscure. N900 or Netwinder, anyone?
>>
>> So to not give the impression that actually *everyone* (from that small subset of people actively reading the kernel list) is happy with that, I think that having support for at least Midway would be useful. On the one hand it's a decent LPAE platform (with memory actually exceeding 4GB), and on the other hand it's something with capable I/O (SATA) and networking, so one can actually stress test the system. Which is the reason I was using that for KVM testing, but even with that probably going away now there remain still some use cases, and be it for general ARM(32) testing.
> 
> Does LPAE with more than 4GB actually need to work if there's not
> another platform out there?

There are ARCH_BRCMSTB platforms that are 32-bit only and have 6GB of
DRAM populated, and those continue to work just fine, though there is no
known use for KVM AFAICT.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-02-18 18:51 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 17:13 [RFC PATCH 00/11] Removing Calxeda platform support Rob Herring
2020-02-18 17:13 ` Rob Herring
2020-02-18 17:13 ` Rob Herring
2020-02-18 17:13 ` [RFC PATCH 01/11] vfio: Remove Calxeda XGMAC reset driver Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-24 13:07   ` Auger Eric
2020-02-24 13:07     ` Auger Eric
2020-02-24 13:07     ` Auger Eric
2020-02-18 17:13 ` [RFC PATCH 02/11] ata: Remove Calxeda AHCI driver Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-20 17:07   ` Mark Langsdorf
2020-02-20 17:07     ` Mark Langsdorf
2020-02-20 17:07     ` Mark Langsdorf
2020-02-18 17:13 ` [RFC PATCH 03/11] cpuidle: Remove Calxeda driver Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:35   ` Daniel Lezcano
2020-02-18 17:35     ` Daniel Lezcano
2020-02-18 17:35     ` Daniel Lezcano
2020-02-18 17:13 ` [RFC PATCH 04/11] cpufreq: " Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-19  1:49   ` Viresh Kumar
2020-02-19  1:49     ` Viresh Kumar
2020-02-19  1:49     ` Viresh Kumar
2020-02-20 17:06   ` Mark Langsdorf
2020-02-20 17:06     ` Mark Langsdorf
2020-02-20 17:06     ` Mark Langsdorf
2020-02-18 17:13 ` [RFC PATCH 05/11] EDAC: Remove Calxeda drivers Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:33   ` Borislav Petkov
2020-02-18 17:33     ` Borislav Petkov
2020-02-18 17:33     ` Borislav Petkov
2020-02-19 11:57   ` Robert Richter
2020-02-19 11:57     ` Robert Richter
2020-02-19 11:57     ` Robert Richter
2020-02-18 17:13 ` [RFC PATCH 06/11] iommu: arm-smmu: Remove Calxeda secure mode quirk Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:20   ` Will Deacon
2020-02-18 17:20     ` Will Deacon
2020-02-18 17:20     ` Will Deacon
2020-02-18 17:32     ` Robin Murphy
2020-02-18 17:32       ` Robin Murphy
2020-02-18 17:32       ` Robin Murphy
2020-02-25 22:01     ` Rob Herring
2020-02-25 22:01       ` Rob Herring
2020-02-25 22:01       ` Rob Herring
2020-02-28 10:04       ` Will Deacon
2020-02-28 10:04         ` Will Deacon
2020-02-28 10:25         ` Andre Przywara
2020-02-28 10:25           ` Andre Przywara
2020-02-28 10:25           ` Andre Przywara
2020-02-28 10:50           ` Will Deacon
2020-02-28 10:50             ` Will Deacon
2020-02-28 13:42             ` Andre Przywara
2020-02-28 13:42               ` Andre Przywara
2020-02-28 13:42               ` Andre Przywara
2020-02-28 13:56               ` Will Deacon
2020-02-28 13:56                 ` Will Deacon
2020-02-28 14:11                 ` Andre Przywara
2020-02-28 14:11                   ` Andre Przywara
2020-02-28 14:11                   ` Andre Przywara
2020-02-18 17:13 ` [RFC PATCH 07/11] net: Remove Calxeda XGMAC driver Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13 ` [RFC PATCH 08/11] clk: Remove Calxeda driver Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-19 17:55   ` Stephen Boyd
2020-02-19 17:55     ` Stephen Boyd
2020-02-18 17:13 ` [RFC PATCH 09/11] ARM: Remove Calxeda platform support Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13 ` [RFC PATCH 10/11] ARM: dts: Remove Calxeda platforms Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13 ` [RFC PATCH 11/11] dt-bindings: Remove Calxeda platforms bindings Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:13   ` Rob Herring
2020-02-18 17:22   ` Will Deacon
2020-02-18 17:22     ` Will Deacon
2020-02-18 17:22     ` Will Deacon
2020-02-18 17:30     ` Rob Herring
2020-02-18 17:30       ` Rob Herring
2020-02-18 17:30       ` Rob Herring
2020-02-18 18:13 ` [RFC PATCH 00/11] Removing Calxeda platform support Andre Przywara
2020-02-18 18:13   ` Andre Przywara
2020-02-18 18:13   ` Andre Przywara
2020-02-18 18:40   ` Rob Herring
2020-02-18 18:40     ` Rob Herring
2020-02-18 18:40     ` Rob Herring
2020-02-18 18:51     ` Florian Fainelli [this message]
2020-02-18 18:51       ` Florian Fainelli
2020-02-18 18:51       ` Florian Fainelli
2020-02-19 22:54   ` Olof Johansson
2020-02-19 22:54     ` Olof Johansson
2020-02-19 22:54     ` Olof Johansson
2020-02-20  1:38     ` André Przywara
2020-02-20  1:38       ` André Przywara
2020-02-20  1:38       ` André Przywara

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=f2b15018-2b88-01b8-14f1-a6c326b10b58@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=axboe@kernel.dk \
    --cc=bp@alien8.de \
    --cc=cohuck@redhat.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=eric.auger@redhat.com \
    --cc=graf@amazon.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=james.morse@arm.com \
    --cc=jdl@jdl.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mbrugger@suse.com \
    --cc=mchehab@kernel.org \
    --cc=mlangsdo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rrichter@marvell.com \
    --cc=sboyd@kernel.org \
    --cc=soc@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=will@kernel.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 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.