From: Will Deacon <will.deacon@arm.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: Andre Przywara <Andre.Przywara@arm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvmtool Makefile: relax arm test
Date: Thu, 10 Sep 2015 11:30:11 +0100 [thread overview]
Message-ID: <20150910103011.GB22439@arm.com> (raw)
In-Reply-To: <CAAqcGH=4MBSuZC2wd9QDR1hH7s0fSm5s-n5unc7cu6h-cjP9UA@mail.gmail.com>
On Thu, Sep 10, 2015 at 06:45:59AM +0100, Riku Voipio wrote:
> On 4 September 2015 at 14:06, Andre Przywara <andre.przywara@arm.com> wrote:
> > On 04/09/15 11:52, Riku Voipio wrote:
> >> On 4 September 2015 at 13:10, Andre Przywara <andre.przywara@arm.com> wrote:
> >>> On 03/09/15 12:20, riku.voipio@linaro.org wrote:
> >>>> From: Riku Voipio <riku.voipio@linaro.org>
> >>>>
> >>>> Currently Makefile accepts only armv7l.* When building kvmtool under 32bit
> >>>> personality on Aarch64 machines, uname -m reports "armv8l", so build fails.
> >>>> We expect doing 32bit arm builds in Aarch64 to become standard the same way
> >>>> people do i386 builds on x86_64 machines.
> >>>>
> >>>> Make the sed test a little more greedy so armv8l becomes acceptable.
> >>>>
> >>>> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
> >>>
> >>> The patch looks OK to me, I just wonder how you do the actual build
> >>> within the linux32 environment?
> >>> Do you have an arm cross compiler installed and set CROSS_COMPILE? Or is
> >>> there a magic compiler (driver) which uses uname -m as well?
> >>> And what would be the difference to setting ARCH=arm as well? Just
> >>> convenience?
> >>
> >> It's just an arm32 chroot, with an native arm32 compiler. The chroot
> >> is on an arm64 machine since these tend to be much faster than arm32
> >> hardware.
> >
> > Oh right, a chroot, didn't think about the obvious ;-)
> > Also it applies to 64-bit kernels with 32-bit root filesystems, I think.
> > So:
> >
> > Acked-by: Andre Przywara <andre.przywara@arm.com>
>
> Ping?
Applied and pushed, thanks.
In future, it's best to Cc me if you want to make sure stuff doesn't
get missed :)
Cheers,
Will
next prev parent reply other threads:[~2015-09-10 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 11:20 [PATCH] kvmtool Makefile: relax arm test riku.voipio
2015-09-04 10:10 ` Andre Przywara
2015-09-04 10:52 ` Riku Voipio
2015-09-04 11:06 ` Andre Przywara
2015-09-10 5:45 ` Riku Voipio
2015-09-10 10:30 ` Will Deacon [this message]
2015-09-10 10:35 ` Riku Voipio
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=20150910103011.GB22439@arm.com \
--to=will.deacon@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=riku.voipio@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.