From: Jan Kiszka <jan.kiszka@web.de>
To: "Thiébaud Weksteen" <thiebaud@weksteen.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scripts/gdb: multi arch lx_current
Date: Tue, 21 Jul 2015 22:48:14 +0200 [thread overview]
Message-ID: <55AEB00E.8000200@web.de> (raw)
In-Reply-To: <55653A0F.2060504@weksteen.fr>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
Hi Thiebaud,
sorry, just realized that this fell through the cracks after vacation
back then.
On 2015-05-27 05:29, Thiébaud Weksteen wrote:
> Hi Jan,
>
> I've been working on lx_current and cpus.py to support other architectures
> than just x86. From my understanding, current/get_current are not available
> with the default debug option (-g). We could either modify that level so that
> the inline functions/macros are available or reimplement part of logic to
> retrieve the current task (sp masking, etc).
>
> Are there any other options to retrieve the current task? What do you
> recommend?
I would prefer the reimplementation like we do elsewhere already.
Debugging should remain minimal invasive to the kernel.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-07-21 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 3:29 scripts/gdb: multi arch lx_current Thiébaud Weksteen
2015-07-21 20:48 ` Jan Kiszka [this message]
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=55AEB00E.8000200@web.de \
--to=jan.kiszka@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thiebaud@weksteen.fr \
/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