From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v3] build: remove shim related targets
Date: Wed, 21 Feb 2018 12:45:01 +0000 [thread overview]
Message-ID: <f5085117-d69e-54e6-053f-e66aa31b19fb@citrix.com> (raw)
In-Reply-To: <20180221122218.37777-1-roger.pau@citrix.com>
On 21/02/18 12:22, Roger Pau Monne wrote:
> There's no need to have shim specific targets, so just use the regular
> xen makefile targets in order to build the shim binary.
>
> When the shim is build as part of the firmware directory install the
> stripped Xen binary to the firmware directory and place a binary with
> symbols in the debug directory.
>
> The objcopy step of the shim build is also removed in this patch:
> since the shim is booted in PVH mode there's no need for the resulting
> binary to be in elf32 format. Xen can load PVH kernels with either a
> 32 or 64bit elf header.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-21 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 12:22 [PATCH v3] build: remove shim related targets Roger Pau Monne
2018-02-21 12:39 ` Wei Liu
2018-02-21 12:45 ` Andrew Cooper [this message]
2018-02-21 13:06 ` Jan Beulich
2018-02-28 11:02 ` Jan Beulich
2018-02-28 11:47 ` Roger Pau Monné
2018-02-28 12:29 ` Jan Beulich
2018-02-28 13:02 ` Roger Pau Monné
2018-02-28 13:25 ` Jan Beulich
2018-02-28 15:02 ` Roger Pau Monné
2018-02-28 15:30 ` Jan Beulich
2018-02-28 15:47 ` Roger Pau Monné
2018-02-28 16:27 ` Jan Beulich
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=f5085117-d69e-54e6-053f-e66aa31b19fb@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.