mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Probir Roy <proy.cse@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	prasad@linux.vnet.ibm.com, paulus@au1.ibm.com,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: Restriction on setting debug registers (HW breakpoint) at kernel space
Date: Wed, 18 Oct 2017 22:43:12 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1710182239360.2477@nanos> (raw)
In-Reply-To: <CALe4XzaNXDz5SPhC2tLszW3dVNq59Ac3JriTG9n5QqVsQT39nw@mail.gmail.com>

On Fri, 13 Oct 2017, Probir Roy wrote:
> I am patching the perf tool of linux to set HW breakpoints at kernel
> space. I found that there is an interface for user-space
> (modify_user_hw_breakpoint) but no interface for system wide
> breakpoint modification. Older version of linux had this support by K.
> Prasad. I was wondering why linux remove this support. Moreover, when
> I patch the perf tool for kernel space breakpoint following steps from
> "modify_user_hw_breakpoint", kernel panics but nothing is written on
> log file. What could be the issue? Is it a race condition while
> modifying the address or is it because kernel restricts it to set HW
> breakpoint at some kernel address(if so, where is it written)?

Can you please provide the patch you use and the perf command line which
causes the kernel to panic?

Also telling which kernel version and hardware system you are using would
be helpful.

Thanks,

	tglx

      reply	other threads:[~2017-10-18 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 14:07 Probir Roy
2017-10-18 20:43 ` Thomas Gleixner [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=alpine.DEB.2.20.1710182239360.2477@nanos \
    --to=tglx@linutronix.de \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@au1.ibm.com \
    --cc=peterz@infradead.org \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=proy.cse@gmail.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
all inboxes | Powered by JetHome®