Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH 2/5] configure.ac, arch/x86_64: handle x32 as subarch of x86_64 and don't specify -mcmodel=large there
Date: Fri, 23 Oct 2020 20:40:26 +0200	[thread overview]
Message-ID: <20201023184023.GA20943@vergenet.net> (raw)
In-Reply-To: <20201023154103.vwhdqxpguzlpvmwq@tarta.nabijaczleweli.xyz>

On Fri, Oct 23, 2020 at 05:41:03PM +0200, Ahelenia Ziemiańska wrote:
> On Fri, Oct 23, 2020 at 04:33:07PM +0200, Simon Horman wrote:
> > On Fri, Oct 09, 2020 at 05:39:42PM +0200, Ahelenia Ziemiańska wrote:
> > > Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> > > ---
> > >  configure.ac                   | 8 ++++++++
> > >  purgatory/arch/x86_64/Makefile | 2 ++
> > >  2 files changed, 10 insertions(+)
> > > 
> > > diff --git a/configure.ac b/configure.ac
> > > index f025823..4e8f7c5 100644
> > > --- a/configure.ac
> > > +++ b/configure.ac
> > > @@ -54,6 +54,14 @@ case $target_cpu in
> > >  		;;
> > >  	ia64|x86_64|alpha|m68k )
> > >  		ARCH="$target_cpu"
> > > +		case $target in
> > > +			*x32 )
> > > +				SUBARCH="x32"
> > > +				;;
> > > +			* )
> > > +				SUBARCH=""
> > > +				;;
> > > +		esac
> > 
> > Is x32 value only for x86_64 or ia64, x886_64, alpha and m68k as
> > seems to be implied by this change?
> 
> There is, indeed, no x32 equivalent for non-amd64,
> but I just put this here like this because there aren't
> any other triples that end in "x32". Would you rather this go
> in a separate "if ARCH=x86_64 && target=*x32" clause below?

Yes, I think that would be slightly nicer.

> > Also, could you let me know how to exercise compiling this changeset?
> 
> The easiest way would be to install GCC for "x86_64-linux-gnux32";
> on Buster, installing gcc-x86-64-linux-gnux32 followed by
>   ./configure --host=x86_64-linux-gnux32
> worked and built.

Thanks, this looks like it should work well for me.
I'll try it out.

> Alternatively, you could use an x32 chroot via something
> along the lines of
>   debootstrap --arch=x32 --variant=minbase
>     --include=debian-ports-archive-keyring --no-check-gpg sid target
>     https://deb.debian.org/debian-ports
> and proceeding as normal within.
> 
> To test the kexecution and/or get the x32 userland to run, you'll need
> your kernel to have CONFIG_X86_X32=y, or, on Debian amd64 kernels,
> to pass syscall.x32=y on the cmdline.
> 
> Best,
> Ahelenia



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2020-10-23 18:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 15:39 [PATCH 0/5] x32 support Ahelenia Ziemiańska
2020-10-09 15:39 ` [PATCH 1/5] config: update to latest config.{sub,guess}, install-sh Ahelenia Ziemiańska
2020-10-09 15:39 ` [PATCH 2/5] configure.ac, arch/x86_64: handle x32 as subarch of x86_64 and don't specify -mcmodel=large there Ahelenia Ziemiańska
2020-10-23 14:33   ` Simon Horman
2020-10-23 15:41     ` Ahelenia Ziemiańska
2020-10-23 18:40       ` Simon Horman [this message]
2020-11-11 12:40         ` Ahelenia Ziemiańska
2020-10-09 15:39 ` [PATCH 3/5] i386/kexec-mb2-x86.c: cast ints to uintptr_t before pointers to avoid warnings Ahelenia Ziemiańska
2020-10-09 15:39 ` [PATCH 4/5] i386: fix string formatting-related warnings Ahelenia Ziemiańska
2020-10-09 15:40 ` [PATCH 5/5] x86_64: allow ELFCLASS32 for x32 support Ahelenia Ziemiańska
2020-11-16 11:00 ` [PATCH 0/5] " Simon Horman

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=20201023184023.GA20943@vergenet.net \
    --to=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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