[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPoiz9xDUb1aoYMfj8jnQRTKo8GCH5PyfNjDd-04=AQXrQjBCA@mail.gmail.com>
Date: Mon, 10 Mar 2014 22:20:45 -0700
From: Jon Mason <jdmason@...zu.us>
To: Muli Ben-Yehuda <muli@...technion.ac.il>
Cc: "H. Peter Anvin" <hpa@...or.com>, WANG Chao <chaowang@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Vivek Goyal <vgoyal@...hat.com>,
Yinghai Lu <yinghai@...nel.org>, Baoquan He <bhe@...hat.com>,
kexec@...ts.infradead.org, discuss@...-64.org, x86@...nel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: How could we get rid of saved_max_pfn for calgary iommu?
On Sun, Mar 9, 2014 at 12:06 AM, Muli Ben-Yehuda <muli@...technion.ac.il> wrote:
> On Thu, Mar 06, 2014 at 07:46:44AM -0700, Jon Mason wrote:
>
>> > 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.
>>
>> It is getting a bit crufty in arch/x86. Would it be better to move
>> it to drivers/iommu?
>
> Not sure I see the potential benefit... I think for Calgary it's
> either leave it in arch/x86 or rip it out.
The intent is for it go where the other IOMMU drivers are, and gain
changes to the overall infrastructure as it evolves. There has been a
decent amount of work going on in there :)
Of course, someone would have to put the effort in and test it.
>
> Cheers,
> Muli
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists