mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>,
	Thomas Glanzmann <thomas@glanzmann.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Baoquan He <bhe@redhat.com>, Borislav Petkov <bp@suse.de>,
	Dave Young <dyoung@redhat.com>,
	Eric Biederman <ebiederm@xmission.com>,
	Greg Kroah-Hartman <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	WANG Chao <chaowang@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
	ubuntu@iam.tj
Subject: Re: REGRESSION: 8fc5b4d: Unable to compile x86_64 kernel with x86_32 userland
Date: Wed, 20 Aug 2014 10:07:01 -0500	[thread overview]
Message-ID: <30d943a9-ba4a-47ee-9333-0ffeea00c3a1@email.android.com> (raw)
In-Reply-To: <20140820125630.GA12786@redhat.com>

It says "32-bit mode" which means it is another issue: we are dropping -m64 at some point.

On August 20, 2014 7:56:30 AM CDT, Vivek Goyal <vgoyal@redhat.com> wrote:
>On Wed, Aug 20, 2014 at 08:24:08AM +0200, Thomas Glanzmann wrote:
>> Hello Vivek,
>> commit 8fc5b4d introduces a regression that no longer allows to
>compile
>> x86_64 kernel under x86_32 userland. TJ on freenode/#kernel did
>analyze
>> it:
>> 
>> > (mini) [~/work/linux-2.6] make
>> > scripts/kconfig/conf --silentoldconfig Kconfig
>> >   CHK     include/config/kernel.release
>> >   UPD     include/config/kernel.release
>> >   CHK     include/generated/uapi/linux/version.h
>> >   CHK     include/generated/utsrelease.h
>> >   UPD     include/generated/utsrelease.h
>> >   CC      arch/x86/purgatory/purgatory.o
>> > arch/x86/purgatory/purgatory.c:1:0: error: code model 'large' not
>supported in the 32 bit mode
>> > make[1]: *** [arch/x86/purgatory/purgatory.o] Error 1
>> > make: *** [archprepare] Error 2
>> 
>> 08:10 < TJ-> Glanzmann: The purgatory code from kexec is specifying
>".code64"
>> 08:11 < TJ-> Glanzmann: so when your local 32-bit linker tries to
>deal with that ... it errors
>> 08:14 < TJ-> Glanzmann: there's only one introducing the purgatory
>stuff
>> 08:14 < TJ-> 8fc5b4d Fri Aug 8 15:57:32 2014 -0700 Vivek Goyal
>purgatory: core purgatory functionality
>
>Hi Thomas,
>
>Thanks for the report. I think this is also happening because purgatory
>is
>right now being compiled with compiler option -mcmodel=large. There was
>another report where older version of gcc did not support
>-mcmodel=large.
>
>A patch is sitting in akpm's tree. That patch puts the new code under
>a new config option CONFIG_KEXEC_FILE. So as long as you don't enable
>CONFIG_KEXEC_FILE=y, you should be fine. This should not impact any of
>the existing functionality. Just that you will not get the benefit of
>new system call.
>
>http://ozlabs.org/~akpm/mmotm/broken-out/kexec-create-a-new-config-option-config_kexec_file-for-new-syscall.patch
>
>I hope this patch gets merged soon.
>
>In the mean time I am trying to figure out how can I move away from
>using -mcmodel=large for purgatory.
>
>Thanks
>Vivek

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.

  reply	other threads:[~2014-08-20 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  6:04 Regression: Can't compile x86_64 with 32 Bit userland: arch/x86/purgatory/purgatory.c:1:0: error: code model 'large' not supported in the 32 bit mode Thomas Glanzmann
2014-08-20  6:24 ` REGRESSION: 8fc5b4d: Unable to compile x86_64 kernel with x86_32 userland Thomas Glanzmann
2014-08-20 12:56   ` Vivek Goyal
2014-08-20 15:07     ` H. Peter Anvin [this message]
2014-08-20 15:48       ` Vivek Goyal
2014-08-20 16:21         ` Thomas Glanzmann
2014-08-20 16:56         ` H. Peter Anvin
2014-08-20 16:16     ` Thomas Glanzmann

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=30d943a9-ba4a-47ee-9333-0ffeea00c3a1@email.android.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bp@suse.de \
    --cc=chaowang@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mjg59@srcf.ucam.org \
    --cc=mtk.manpages@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=thomas@glanzmann.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ubuntu@iam.tj \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@kernel.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®