How could we get rid of saved_max_pfn for calgary iommu?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: How could we get rid of saved_max_pfn for calgary iommu?
From: muli@xxxxxxxxxxxxxxxxx (Muli Ben-Yehuda)
Date: Thu, 6 Mar 2014 09:00:47 +0200
In-reply-to: <53181AC1.2020807@zytor.com>
References: <20140219061824.GA29703@dhcp-17-89.nay.redhat.com> <20140305053617.GE26240@dhcp-17-89.nay.redhat.com> <20140306064756.GB16859@needle.mulix.org> <53181AC1.2020807@zytor.com>

On Wed, Mar 05, 2014 at 10:50:41PM -0800, H. Peter Anvin wrote:

> OK, second question... is it time to axe Calgary?

I don't know of anyone still using it, but it's not
impossible. Calgary and CalIOC2 machines would now be ~5-8 years old.

Cheers,
Muli

Follow-Ups:
- How could we get rid of saved_max_pfn for calgary iommu?
  - From: Jon Mason

References:
- How could we get rid of saved_max_pfn for calgary iommu?
  - From: WANG Chao
- How could we get rid of saved_max_pfn for calgary iommu?
  - From: WANG Chao
- How could we get rid of saved_max_pfn for calgary iommu?
  - From: Muli Ben-Yehuda
- How could we get rid of saved_max_pfn for calgary iommu?
  - From: H. Peter Anvin

Prev by Date: How could we get rid of saved_max_pfn for calgary iommu?
Next by Date: [ANNOUNCE] kexec-tools 2.0.6
Previous by thread: How could we get rid of saved_max_pfn for calgary iommu?
Next by thread: How could we get rid of saved_max_pfn for calgary iommu?
Index(es):
- Date
- Thread

[Index of Archives] [LM Sensors] [Linux Sound] [ALSA Users] [ALSA Devel] [Linux Audio Users] [Linux Media] [Kernel] [Gimp] [Yosemite News] [Linux Media]

Powered by Linux