[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVtZg6O4e6yH_yNfGcm0dqJOp1=Mh8iN3y4GAL4vH=5QA@mail.gmail.com>
Date: Fri, 4 Jan 2013 20:10:29 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Shuah Khan <shuahkhan@...il.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Borislav Petkov <bp@...en8.de>, Jan Kiszka <jan.kiszka@....de>,
Jason Wessel <jason.wessel@...driver.com>,
linux-kernel@...r.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Joerg Roedel <joro@...tes.org>
Subject: Re: [PATCH v7u1 26/31] x86: Don't enable swiotlb if there is not
enough ram for it
On Fri, Jan 4, 2013 at 6:02 PM, Shuah Khan <shuahkhan@...il.com> wrote:
> I applied your patch to 3.6.11 and changed the panic() to pr_info()
> and also changed enough_mem_for_swiotlb() to always return false to
> simulate not enough memory condition as this system does have enough
> memory.
>
> So at least on this AMD system, your patch will result in a panic.
ok, thanks for testing.
if enough_mem_for_swiotlb() return false really, allocating buffer
for swiotlb with bootmem would panic already, right?
so this patch just delay the panic a while for AMD system with
unhandled devices by IOMMU.
Thanks
Yinghai
--
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