From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kieran Bingham <kieran.bingham@linaro.org>, linux-kernel@vger.kernel.org
Cc: lee.jones@linaro.org, peter.griffin@linaro.org,
maxime.coquelin@st.com, mmarek@suse.com,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCHv4 01/12] scripts/gdb: Provide linux constants
Date: Wed, 30 Mar 2016 23:02:18 +0200 [thread overview]
Message-ID: <56FC3EDA.5030701@siemens.com> (raw)
In-Reply-To: <1459339251-29611-2-git-send-email-kieran.bingham@linaro.org>
On 2016-03-30 14:00, Kieran Bingham wrote:
> Some macro's and defines are needed when parsing memory, and without
> compiling the kernel as -g3 they are not available in the debug-symbols.
>
> We use the pre-processor here to extract constants to a dedicated module
> for the linux debugger extensions
>
> Top level Kbuild is used to call in and generate the constants file,
> while maintaining dependencies on autogenerated files in
> include/generated
>
> CC: mmarek@suse.com
> CC: linux-kbuild@vger.kernel.org
>
> Signed-off-by: Kieran Bingham <kieran.bingham@linaro.org>
> ---
> Changes since v1:
>
> Kbuild:
> - Call to generate constants_py with dependancy on generated files
>
> scripts/gdb/linux/Makefile:
> - Use call if_changed, and correct quiet invocation
> - Annouce "GEN $@" instead of GDB PP
>
> scripts/gdb/linux/constants.py.in:
> - Updated to use better macro implementations for one line defines
> ---
Please only use a single separator line (i.e. remove this one), or the
history blob above makes it into the commit log. But there is no need to
resend if that will remain the only remark.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2016-03-30 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 12:00 [PATCHv4 00/12] gdb/scripts: Linux awareness debug commands Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 01/12] scripts/gdb: Provide linux constants Kieran Bingham
2016-03-30 21:02 ` Jan Kiszka [this message]
2016-03-30 12:00 ` [PATCHv4 02/12] scripts/gdb: Provide kernel list item generators Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 03/12] scripts/gdb: Convert modules usage to lists functions Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 04/12] scripts/gdb: Provide exception catching parser Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 05/12] scripts/gdb: Support !CONFIG_MODULES gracefully Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 06/12] scripts/gdb: Provide a dentry_name VFS path helper Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 07/12] scripts/gdb: Add io resource readers Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 08/12] scripts/gdb: Add mount point list command Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 09/12] scripts/gdb: Add cpu iterators Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 10/12] scripts/gdb: Add a Radix Tree Parser Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 11/12] scripts/gdb: Add documentation example for radix tree Kieran Bingham
2016-03-30 12:00 ` [PATCHv4 12/12] scripts/gdb: Add lx_thread_info_by_pid helper Kieran Bingham
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=56FC3EDA.5030701@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kieran.bingham@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=mmarek@suse.com \
--cc=peter.griffin@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.