From: Ingo Molnar <mingo@elte.hu>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: ak@suse.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, markus.t.metzger@gmail.com,
suresh.b.siddha@intel.com, roland@redhat.com,
akpm@linux-foundation.org, mtk.manpages@gmail.com
Subject: Re: [patch 1/5] x86, ptrace: rlimit BTS buffer allocation
Date: Thu, 20 Dec 2007 15:32:59 +0100 [thread overview]
Message-ID: <20071220143259.GA21803@elte.hu> (raw)
In-Reply-To: <20071220140530.A29536@sedona.ch.intel.com>
* Markus Metzger <markus.t.metzger@intel.com> wrote:
> Check the rlimit of the tracing task for total and locked memory when
> allocating the BTS buffer.
thanks, i've picked up your patches into x86.git. I suspect if/once
Roland has any objections on the API we'd have to resolve those - but to
me it looks quite usable at the moment.
Ingo
prev parent reply other threads:[~2007-12-20 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 13:05 [patch 1/5] x86, ptrace: rlimit BTS buffer allocation Markus Metzger
2007-12-20 14:32 ` Ingo Molnar [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=20071220143259.GA21803@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mtk.manpages@gmail.com \
--cc=roland@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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