[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5415A4DF.90706@redhat.com>
Date: Sun, 14 Sep 2014 16:23:27 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>
CC: kvm@...r.kernel.org,
Christoffer Dall <christoffer.dall@...aro.org>,
linux-mm@...ck.org, linux-s390@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-mips@...ux-mips.org, ralf@...ux-mips.org,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com
Subject: Re: [PATCH] mm: export symbol dependencies of is_zero_pfn()
Il 12/09/2014 23:19, Ard Biesheuvel ha scritto:
> On 12 September 2014 23:14, Andrew Morton <akpm@...ux-foundation.org> wrote:
>> On Fri, 12 Sep 2014 22:17:23 +0200 Ard Biesheuvel <ard.biesheuvel@...aro.org> wrote:
>>
>>> In order to make the static inline function is_zero_pfn() callable by
>>> modules, export its symbol dependencies 'zero_pfn' and (for s390 and
>>> mips) 'zero_page_mask'.
>>
>> So hexagon and score get the export if/when needed.
>>
>
> Exactly.
>
>>> We need this for KVM, as CONFIG_KVM is a tristate for all supported
>>> architectures except ARM and arm64, and testing a pfn whether it refers
>>> to the zero page is required to correctly distinguish the zero page
>>> from other special RAM ranges that may also have the PG_reserved bit
>>> set, but need to be treated as MMIO memory.
>>>
>>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>
>>> ---
>>> arch/mips/mm/init.c | 1 +
>>> arch/s390/mm/init.c | 1 +
>>> mm/memory.c | 2 ++
>>
>> Looks OK to me. Please include the patch in whichever tree is is that
>> needs it, and merge it up via that tree.
>>
>
> Thanks.
>
> @Paolo: could you please take this (with Andrew's ack), and put it
> before the patch you took earlier today?
Yes, will do.
Paolo
--
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