linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Glanzmann <thomas@glanzmann.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: REGRESSION: 8fc5b4d: Unable to compile x86_64 kernel with x86_32 userland
Date: Wed, 20 Aug 2014 18:16:45 +0200	[thread overview]
Message-ID: <20140820161645.GA25390@glanzmann.de> (raw)
In-Reply-To: <20140820125630.GA12786@redhat.com>

Hello Vivek,

* Vivek Goyal <vgoyal@redhat.com> [2014-08-20 15:53]:
> 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.

perfect. I tried the patch and with the patch the kernel compiles again.

Cheers,
        Thomas

      parent reply	other threads:[~2014-08-20 16:16 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
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 [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=20140820161645.GA25390@glanzmann.de \
    --to=thomas@glanzmann.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).