All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH 2/2] selftests: New x86 breakpoints selftest
Date: Mon, 12 Dec 2011 11:36:11 +0530	[thread overview]
Message-ID: <20111212060611.GA18998@in.ibm.com> (raw)
In-Reply-To: <1322840475-19553-2-git-send-email-fweisbec@gmail.com>

On Fri, Dec 02, 2011 at 04:41:15PM +0100, Frederic Weisbecker wrote:
> Bring a first selftest in the relevant directory. This tests
> several combinations of breakpoints and watchpoints in x86, as
> well as icebp traps and int3 traps. Given the amount of breakpoint
> regressions we raised after we merged the generic breakpoint
> infrastructure, such selftest became necessary and can still serve
> today as a basis for new patches that touch the do_debug() path.
> 


Hi Frederic,
	Can we also including testing of watchpoints over kernel variables?
We could do this using the perf syscall or (in a convoluted way) use a
kernel module that works in tandem with this user-space testcase.

Thanks,
K.Prasad


  parent reply	other threads:[~2011-12-12  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 15:41 [PATCH 1/2] selftests: New very basic kernel selftests directory Frederic Weisbecker
2011-12-02 15:41 ` [PATCH 2/2] selftests: New x86 breakpoints selftest Frederic Weisbecker
2011-12-07 23:32   ` Andrew Morton
2011-12-08  0:11     ` Frederic Weisbecker
2011-12-12  6:06   ` K.Prasad [this message]
2012-01-13 18:54 ` [PATCH 1/2] selftests: New very basic kernel selftests directory Fubo Chen
2012-01-17  1:49   ` Frederic Weisbecker

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=20111212060611.GA18998@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@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 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.