From: Muli Ben-Yehuda <muli@cs.technion.ac.il>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: discuss@x86-64.org, Baoquan He <bhe@redhat.com>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, WANG Chao <chaowang@redhat.com>,
"Jon D. Mason" <jdmason@kudzu.us>,
Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: How could we get rid of saved_max_pfn for calgary iommu?
Date: Thu, 6 Mar 2014 09:00:47 +0200 [thread overview]
Message-ID: <20140306070047.GF16859@needle.mulix.org> (raw)
In-Reply-To: <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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Muli Ben-Yehuda <muli@cs.technion.ac.il>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: WANG Chao <chaowang@redhat.com>,
"Jon D. Mason" <jdmason@kudzu.us>,
Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, discuss@x86-64.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: How could we get rid of saved_max_pfn for calgary iommu?
Date: Thu, 6 Mar 2014 09:00:47 +0200 [thread overview]
Message-ID: <20140306070047.GF16859@needle.mulix.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2014-03-06 7:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 6:18 How could we get rid of saved_max_pfn for calgary iommu? WANG Chao
2014-02-19 6:18 ` WANG Chao
2014-02-20 0:04 ` Jon Mason
2014-02-20 0:04 ` Jon Mason
2014-02-20 2:36 ` Vivek Goyal
2014-02-20 2:36 ` Vivek Goyal
2014-02-21 7:47 ` WANG Chao
2014-02-21 7:47 ` WANG Chao
2014-02-21 8:18 ` Baoquan He
2014-02-21 8:18 ` Baoquan He
2014-03-05 5:36 ` WANG Chao
2014-03-05 5:36 ` WANG Chao
2014-03-06 6:47 ` Muli Ben-Yehuda
2014-03-06 6:47 ` Muli Ben-Yehuda
2014-03-06 6:50 ` H. Peter Anvin
2014-03-06 6:50 ` H. Peter Anvin
2014-03-06 7:00 ` Muli Ben-Yehuda [this message]
2014-03-06 7:00 ` Muli Ben-Yehuda
2014-03-06 14:46 ` Jon Mason
2014-03-06 14:46 ` Jon Mason
2014-03-09 7:06 ` Muli Ben-Yehuda
2014-03-09 7:06 ` Muli Ben-Yehuda
2014-03-11 5:20 ` Jon Mason
2014-03-11 5:20 ` Jon Mason
2014-03-06 16:05 ` Vivek Goyal
2014-03-06 16:05 ` Vivek Goyal
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=20140306070047.GF16859@needle.mulix.org \
--to=muli@cs.technion.ac.il \
--cc=bhe@redhat.com \
--cc=chaowang@redhat.com \
--cc=discuss@x86-64.org \
--cc=hpa@zytor.com \
--cc=jdmason@kudzu.us \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--cc=yinghai@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.