From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] btrace: kernel address filtering
Date: Tue, 08 Sep 2015 12:21:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23331AB211@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <55EEB763.2060701@redhat.com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Tuesday, September 8, 2015 12:25 PM
> To: Metzger, Markus T
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH] btrace: kernel address filtering
>
> On 09/01/2015 04:42 PM, Markus Metzger wrote:
>
> > --- a/gdb/nat/linux-btrace.h
> > +++ b/gdb/nat/linux-btrace.h
> > @@ -101,10 +101,11 @@ struct btrace_target_info
> > } variant;
> > #endif /* HAVE_LINUX_PERF_EVENT_H */
> >
> > - /* The size of a pointer in bits for this thread.
> > - The information is used to identify kernel addresses in order to skip
> > - records from/to kernel space. */
> > - int ptr_bits;
> > + /* The kernel start address.
> > + The information is used to tell kernel addresses from user addresses in
> > + order to skip records from kernel space. We assume that any address
> > + smaller than KERNEL_START is in user space. */
> > + uint64_t kernel_start;
>
> Is there a reason we need to store the kernel's start address on every
> thread?
I don't think we need to store it, at all. We had to store the ptr_bits since we
needed to fill them in later. But the kernel start address is computed, cached,
and used in nat/linux-btrace.c.
I'll send an updated patch.
thanks,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2015-09-08 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:42 Markus Metzger
2015-09-08 10:24 ` Pedro Alves
2015-09-08 12:21 ` Metzger, Markus T [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=A78C989F6D9628469189715575E55B23331AB211@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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