From: Vivek Goyal <vgoyal@redhat.com>
To: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: ananth@in.ibm.com, mahesh@linux.vnet.ibm.com,
kexec@lists.infradead.org, LChouinard@s2sys.com,
tachibana@mxm.nes.nec.co.jp, kumagai-atsushi@mxc.nes.nec.co.jp,
buendgen@de.ibm.com
Subject: Re: [PATCH v2 1/7] Initialize and setup eppic
Date: Thu, 15 Nov 2012 11:04:56 -0500 [thread overview]
Message-ID: <20121115160456.GG2529@redhat.com> (raw)
In-Reply-To: <20121108133804.28410.99166.stgit@aravinda>
On Thu, Nov 08, 2012 at 07:08:04PM +0530, Aravinda Prasad wrote:
[..]
> diff --git a/Makefile b/Makefile
> index d5fc09e..3ac8e63 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -55,6 +55,13 @@ LIBS := -llzo2 $(LIBS)
> CFLAGS += -DUSELZO
> endif
>
> +ifeq ($(EPPIC), on)
> +LIBS := -leppic -ltinfo $(LIBS)
So you also pull in libarary "tinfo". Does that 1MB number include this
too? What's the total size bloat for makedumpfile once we compile with
EPPIC on.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-11-15 16:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 13:37 [PATCH v2 0/7] makedumpfile security key filtering with eppic Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 1/7] Initialize and setup eppic Aravinda Prasad
2012-11-15 16:04 ` Vivek Goyal [this message]
2012-11-16 9:43 ` Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 2/7] makedumpfile and eppic interface layer Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 3/7] Eppic call back functions to query a dump image Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 4/7] Implement apigetctype call back function Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 5/7] Implement apimember and apigetrtype call back functions Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 6/7] Extend eppic built-in functions to include memset function Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 7/7] Support fully typed symbol access mode Aravinda Prasad
2012-11-14 1:15 ` [PATCH v2 0/7] makedumpfile security key filtering with eppic Atsushi Kumagai
2012-11-14 14:54 ` Vivek Goyal
2012-11-14 17:06 ` Aravinda Prasad
2012-11-14 17:53 ` Vivek Goyal
2012-11-15 12:50 ` Aravinda Prasad
2012-11-15 14:27 ` Dave Anderson
2012-11-15 15:55 ` Vivek Goyal
2012-11-16 9:52 ` Aravinda Prasad
2012-11-16 14:36 ` Vivek Goyal
2012-11-20 9:47 ` Atsushi Kumagai
2012-11-21 7:19 ` Aravinda Prasad
2012-11-21 13:57 ` Vivek Goyal
2012-11-22 17:14 ` Aravinda Prasad
2012-11-26 14:04 ` Vivek Goyal
2012-12-03 6:02 ` Aravinda Prasad
2012-12-03 13:20 ` Vivek Goyal
2012-12-03 14:35 ` Aravinda Prasad
2012-12-03 18:40 ` Vivek Goyal
2012-12-04 8:36 ` Atsushi Kumagai
2012-12-04 8:56 ` Aravinda Prasad
2012-12-06 15:26 ` Dave Anderson
2012-12-07 6:05 ` Aravinda Prasad
2012-12-07 13:46 ` Luc Chouinard
2012-12-07 21:59 ` Vivek Goyal
2012-12-10 7:32 ` Aravinda Prasad
2012-12-10 11:35 ` Aravinda Prasad
2012-11-16 9:49 ` Aravinda Prasad
2012-11-15 15:49 ` Vivek Goyal
2012-11-16 11:10 ` Aravinda Prasad
2012-11-16 14:59 ` Vivek Goyal
2012-11-14 20:15 ` Vivek Goyal
2012-11-15 12:55 ` Aravinda Prasad
2012-11-14 20:21 ` Dave Anderson
2012-11-15 13:27 ` Aravinda Prasad
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=20121115160456.GG2529@redhat.com \
--to=vgoyal@redhat.com \
--cc=LChouinard@s2sys.com \
--cc=ananth@in.ibm.com \
--cc=aravinda@linux.vnet.ibm.com \
--cc=buendgen@de.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=mahesh@linux.vnet.ibm.com \
--cc=tachibana@mxm.nes.nec.co.jp \
/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