From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Luis Machado <lgustavo@codesourcery.com>,
Philipp Rudo <prudo@linux.vnet.ibm.com>,
gdb-patches@sourceware.org, peter.griffin@linaro.org,
yao.qi@arm.com
Subject: Re: [RFC 7/7] Add S390 support for linux-kernel target
Date: Mon, 06 Feb 2017 18:48:00 -0000 [thread overview]
Message-ID: <m3efzbnoke.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <20170206155222.GF11916@E107787-LIN> (Yao Qi's message of "Mon, 6 Feb 2017 15:52:22 +0000")
On Mon, Feb 06 2017, Yao Qi wrote:
> On 17-01-12 11:08:59, Luis Machado wrote:
>> On 01/12/2017 05:32 AM, Philipp Rudo wrote:
>> >
>> >diff --git a/gdb/s390-linux-tdep.c b/gdb/s390-linux-tdep.c
>> >index 054c6d5..f436a74 100644
>> >--- a/gdb/s390-linux-tdep.c
>> >+++ b/gdb/s390-linux-tdep.c
>>
>> I wonder if we should put the new lk-specific code in its own file,
>> like s390-lk-tdep.c or something. It would make thing a bit more
>> clear and would pollute the current s390-linux-tdep.c file?
>>
>
> +1.
+1.
The Linux kernel runtime will be the second "operating system" supported
by GDB for the s390/s390x architectures. So if we stick to the usual
naming, we will have three components instead of one:
1. s390-tdep -- common
2. s390-linux-tdep -- Linux user-space-specific
3. s390-lk-tdep -- Linux kernel-specific
--
Andreas
next prev parent reply other threads:[~2017-02-06 18:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 11:32 [RFC 0/7] Support for Linux kernel debugging Philipp Rudo
2017-01-12 11:32 ` [RFC 3/7] Add basic Linux kernel support Philipp Rudo
2017-02-07 10:54 ` Yao Qi
2017-02-07 15:04 ` Philipp Rudo
2017-02-07 17:39 ` Yao Qi
2017-02-09 9:54 ` Philipp Rudo
2017-02-09 13:06 ` Yao Qi
2017-01-12 11:32 ` [RFC 5/7] Add commands for linux-kernel target Philipp Rudo
2017-01-12 11:32 ` [RFC 1/7] Convert substitute_path_component to C++ Philipp Rudo
2017-01-12 11:32 ` [RFC 2/7] Add libiberty/concat styled concat_path function Philipp Rudo
2017-01-12 12:00 ` Pedro Alves
2017-01-12 13:33 ` Philipp Rudo
2017-01-12 13:48 ` Pedro Alves
2017-01-12 15:09 ` Philipp Rudo
2017-01-12 15:42 ` Pedro Alves
2017-01-12 11:32 ` [RFC 6/7] Add privileged registers for s390x Philipp Rudo
2017-01-12 11:32 ` [RFC 7/7] Add S390 support for linux-kernel target Philipp Rudo
2017-01-12 17:09 ` Luis Machado
2017-01-13 11:46 ` Philipp Rudo
2017-02-06 15:52 ` Yao Qi
2017-02-06 18:48 ` Andreas Arnez [this message]
2017-01-12 12:56 ` [RFC 0/7] Support for Linux kernel debugging Philipp Rudo
2017-01-12 13:02 ` [RFC 4/7] Add kernel module support for linux-kernel target Philipp Rudo
2017-01-25 18:10 ` [RFC 0/7] Support for Linux kernel debugging Peter Griffin
2017-01-26 13:12 ` Philipp Rudo
2017-02-03 17:45 ` Yao Qi
2017-02-03 19:46 ` Andreas Arnez
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=m3efzbnoke.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=peter.griffin@linaro.org \
--cc=prudo@linux.vnet.ibm.com \
--cc=qiyaoltc@gmail.com \
--cc=yao.qi@arm.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