mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Adrian Bunk <bunk@stusta.de>
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: [2.6 patch] i386 KEXEC must depend on X86_CMPXCHG64
Date: Thu, 17 Nov 2005 18:47:27 -0700	[thread overview]
Message-ID: <m14q6aohg0.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051117235700.GJ11494@stusta.de> (Adrian Bunk's message of "Fri, 18 Nov 2005 00:57:00 +0100")

Adrian Bunk <bunk@stusta.de> writes:

> This patch fixes the following compile error with 
> CONFIG_X86_CMPXCHG64=n:
>
> <--  snip  -->
>
> ...
>   CC      arch/i386/kernel/machine_kexec.o
> arch/i386/kernel/machine_kexec.c: In function 'identity_map_page':
> arch/i386/kernel/machine_kexec.c:78: error: implicit declaration of function
> 'set_64bit'
> make[1]: *** [arch/i386/kernel/machine_kexec.o] Error 1
>
> <--  snip  -->

Good catch but wrong fix.  This code works fine on a 386.  Or
it did last time I tried it.

This dependency only exists if 3 level page tables are configured.
CONFIG_X86_PAE

The call to set_64bit is a specialized version of set_pmd.
Which also uses set_64_bit.  So I don't see how your kernel can
even build without this.

The only way I can see this even being selected is building
a kernel for a 386 or 486 and wanting pae support.  Which won't
work on a 386 or a 486.  Making it a pointless exercise.

So I think either the pgtable-3level.h needs to fixed,
or we just make CONFIG_HIGHME64G depend on CONFIG_X86_CMPXCHG64.

Eric

  reply	other threads:[~2005-11-18  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 23:57 Adrian Bunk
2005-11-18  1:47 ` Eric W. Biederman [this message]
2006-01-28 16:49   ` [2.6 patch] i386: HIGHMEM64G " Adrian Bunk

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=m14q6aohg0.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=bunk@stusta.de \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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

all inboxes | Powered by JetHome®