From: Dave Jiang <dave.jiang@intel.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, labbott@redhat.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm,x86: fix SMP x86 32bit build for native_pud_clear()
Date: Mon, 27 Feb 2017 12:35:30 -0700 [thread overview]
Message-ID: <ad15f426-62b5-95fa-2168-00b66dde0401@intel.com> (raw)
In-Reply-To: <1488223776-10326-1-git-send-email-boris.ostrovsky@oracle.com>
On 02/27/2017 12:29 PM, Boris Ostrovsky wrote:
>> On 02/15/2017 12:31 PM, Dave Jiang wrote:
>>> The fix introduced by e4decc90 to fix the UP case for 32bit x86, however
>>> that broke the SMP case that was working previously. Add ifdef so the dummy
>>> function only show up for 32bit UP case only.
>>>
>>> Fix: e4decc90 mm,x86: native_pud_clear missing on i386 build
>>>
>>> Reported-by: Alexander Kapshuk <alexander.kapshuk@gmail.com>
>>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>>> ---
>>> arch/x86/include/asm/pgtable-3level.h | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/arch/x86/include/asm/pgtable-3level.h b/arch/x86/include/asm/pgtable-3level.h
>>> index 50d35e3..8f50fb3 100644
>>> --- a/arch/x86/include/asm/pgtable-3level.h
>>> +++ b/arch/x86/include/asm/pgtable-3level.h
>>> @@ -121,9 +121,11 @@ static inline void native_pmd_clear(pmd_t *pmd)
>>> *(tmp + 1) = 0;
>>> }
>>>
>>> +#ifndef CONFIG_SMP
>>> static inline void native_pud_clear(pud_t *pudp)
>>> {
>>> }
>>> +#endif
>>>
>>> static inline void pud_clear(pud_t *pudp)
>>> {
>>>
>
>>
>> This breaks one of the Fedora configurations as of
>> e5d56efc97f8240d0b5d66c03949382b6d7e5570
>>
>> In file included from ./include/linux/mm.h:68:0,
>> from ./include/linux/highmem.h:7,
>> from ./include/linux/bio.h:21,
>> from ./include/linux/writeback.h:205,
>> from ./include/linux/memcontrol.h:30,
>> from ./include/linux/swap.h:8,
>> from ./include/linux/suspend.h:4,
>> from arch/x86/kernel/asm-offsets.c:12:
>> ./arch/x86/include/asm/pgtable.h: In function 'native_local_pudp_get_and_clear':
>> ./arch/x86/include/asm/pgtable.h:888:2: error: implicit declaration of function 'native_pud_clear';did you mean 'native_pmd_clear'? [-Werror=implicit-function-declaration]
>> native_pud_clear(pudp);
>> ^~~~~~~~~~~~~~~~
>>
>> Kernel configuration attached. I'm probably just going to revert
>> this part unless someone sends me a better fix.
>
>
> This breakage happens when CONFIG_HIGHMEM64G (i.e. CONFIG_X86_PAE) and CONFIG_PARAVIRT.
Thanks for the additional breakage configs report. I think I need to
extend that ifdef to additional configs. I'll send out a fix as soon as
I test the various different combination of configs.
>
> -boris
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-02-27 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 20:31 [PATCH] mm,x86: fix SMP x86 32bit build for native_pud_clear() Dave Jiang
2017-02-16 15:42 ` Dave Hansen
2017-02-16 16:27 ` Dave Jiang
2017-02-27 18:31 ` Laura Abbott
2017-02-27 19:29 ` Boris Ostrovsky
2017-02-27 19:35 ` Dave Jiang [this message]
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=ad15f426-62b5-95fa-2168-00b66dde0401@intel.com \
--to=dave.jiang@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox