From: Shuah Khan <shuahkh@osg.samsung.com>
To: Josh Triplett <josh@joshtriplett.org>,
Tim Bird <tim.bird@sonymobile.com>
Cc: "linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v6] selftest: size: Add size test for Linux kernel
Date: Wed, 03 Dec 2014 17:50:11 -0700 [thread overview]
Message-ID: <547FAFC3.40609@osg.samsung.com> (raw)
In-Reply-To: <20141204003653.GA5004@thin>
On 12/03/2014 05:36 PM, Josh Triplett wrote:
> On Wed, Dec 03, 2014 at 10:42:21AM -0800, Tim Bird wrote:
>> This test shows the amount of memory used by the system.
>> Note that this is dependent on the user-space that is loaded
>> when this program runs. Optimally, this program would be
>> run as the init program itself.
>>
>> The program is optimized for size itself, to avoid conflating
>> its own execution with that of the system software.
>> The code is compiled statically, with no stdlibs. On my x86_64 system,
>> this results in a statically linked binary of less than 5K.
>>
>> Signed-off-by: Tim Bird <tim.bird@sonymobile.com>
>
> v6 looks good to me.
>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
>
> Should this go through the tinification tree or the selftests tree?
>
Josh/Tim,
Thanks both. Yes v6 looks good. I will take this through kselftest
tree. I will apply this to kselftes fixes.
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2014-12-04 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 18:42 [PATCH v6] selftest: size: Add size test for Linux kernel Tim Bird
2014-12-04 0:36 ` Josh Triplett
2014-12-04 0:50 ` Shuah Khan [this message]
2014-12-04 2:33 ` Shuah Khan
2014-12-04 16:56 ` RFC: kselftest size roadmap Tim Bird
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=547FAFC3.40609@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tim.bird@sonymobile.com \
/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