From: Christopher Clark <christopher.w.clark@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] firmware/shim : filter output files during Xen tree setup
Date: Tue, 24 Jul 2018 17:21:40 -0700 [thread overview]
Message-ID: <CACMJ4GYhRyZkESCw+OWrW5WbM+LAf6ZCyrbtTrK_12wdMPDyWw@mail.gmail.com> (raw)
In-Reply-To: <5B56F4D802000078001D7155@prv1-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1655 bytes --]
On Tue, Jul 24, 2018 at 2:43 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 20.07.18 at 23:15, <christopher.w.clark@gmail.com> wrote:
> > Exclude named output files from the Xen tree setup.
> >
> > The linkfarm.stamp content will differ between top level "make"
> > and "make install" invocations, due to the introduction of these
> > output files that are produced during the "make" build.
> >
> > Filter these out to prevent an unnecessary rebuild of the shim during
> > "make install".
> >
> > Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com>
> > ---
> > tools/firmware/xen-dir/Makefile | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/firmware/xen-dir/Makefile
> > b/tools/firmware/xen-dir/Makefile
> > index 84648c3..e490dca 100644
> > --- a/tools/firmware/xen-dir/Makefile
> > +++ b/tools/firmware/xen-dir/Makefile
> > @@ -11,6 +11,9 @@ D=xen-root
> > LINK_DIRS=config xen
> > LINK_FILES=Config.mk
> >
> > +# Files to exclude from the link farm
> > +EXCLUDE_FILES=xen xen.gz xen-syms xen-syms.map efi.lds xen.lds mkelf32
> mkreloc
>
> What about xen.efi and all of its auxiliary files?
Fair point - this list was from a non-EFI build, and EFI does add two more
files to it: xen.efi and xen.efi.map
> What about other generated files?
>
I don't see any others being added to the stamp file -- with the possible
exception of the "disabled" file in xen/arch/x86/efi which can capture
build errors. I don't think that file will be present in production builds.
Did you have any others in mind? I'll post an updated patch with the
EFI-updated list in the meantime.
Christopher
[-- Attachment #1.2: Type: text/html, Size: 2653 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-25 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 21:15 [PATCH] firmware/shim : filter output files during Xen tree setup Christopher Clark
2018-07-23 8:17 ` Wei Liu
2018-07-23 9:09 ` Roger Pau Monné
2018-07-23 9:26 ` Andrew Cooper
2018-07-23 23:00 ` Christopher Clark
2018-07-24 9:43 ` Jan Beulich
2018-07-25 0:21 ` Christopher Clark [this message]
2018-07-25 0:28 ` [PATCH v2] " Christopher Clark
[not found] ` <5B57C29F0200000804C77BEC@prv1-mh.provo.novell.com>
[not found] ` <5B57C462020000E403D61C84@prv1-mh.provo.novell.com>
2018-07-25 8:10 ` Jan Beulich
2018-07-26 21:10 ` Christopher Clark
2018-07-25 7:51 ` [PATCH] " 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=CACMJ4GYhRyZkESCw+OWrW5WbM+LAf6ZCyrbtTrK_12wdMPDyWw@mail.gmail.com \
--to=christopher.w.clark@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--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 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).