mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	"K.Prasad" <prasad@linux.vnet.ibm.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, utrace-devel@redhat.com
Subject: Re: x86: do_debug && PTRACE_SINGLESTEP broken by 08d68323d1f0c34452e614263b212ca556dae47f
Date: Fri, 18 Dec 2009 12:05:03 -0800 (PST)	[thread overview]
Message-ID: <20091218200503.2CA0DF9A4@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of  Friday, 18 December 2009 18:27:47 +0100 <20091218172747.GA10924@redhat.com>

> Please find the trivial test-case below. It hangs, because
> PTRACE_SINGLESTEP doesn't trigger the trap.

2.6.33-rc1 x86-64 works for me with either -m64 or -m32 version of that test.

> (not sure this matters, but I did the testing under kvm)

Apparently it does.  You should hack some printks into do_debug() and see
how kvm is differing from real hardware.  (Actually you can probably do
this with a notifier added by a module, not that you are shy about
recompiling!)  

Probably kvm's emulation of the hardware behavior wrt the DR6 bits is not
sufficiently faithful.  Conceivably, kvm is being consistent with some
older hardware and we have encoded assumptions that only newer hardware
meets.  But I'd guess it's just a plain kvm bug.


Thanks,
Roland

  parent reply	other threads:[~2009-12-18 20:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  0:56 Oleg Nesterov
2009-12-18  1:40 ` Roland McGrath
2009-12-18  2:10   ` Oleg Nesterov
2009-12-18  2:58     ` Frederic Weisbecker
2009-12-18  3:09       ` Frederic Weisbecker
2009-12-18  3:53     ` Roland McGrath
2009-12-18  3:06 ` Frederic Weisbecker
2009-12-18 17:27   ` Oleg Nesterov
2009-12-18 17:58     ` K.Prasad
2009-12-18 18:24       ` Oleg Nesterov
2009-12-18 20:05     ` Roland McGrath [this message]
2009-12-18 22:32       ` Oleg Nesterov
2009-12-21 10:22         ` Jan Kiszka
2009-12-21 16:53           ` Oleg Nesterov
2009-12-21 16:48             ` Jan Kiszka
2009-12-18 23:15       ` Frederic Weisbecker
2009-12-20  8:30         ` Avi Kivity
2009-12-18 17:37 ` K.Prasad

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=20091218200503.2CA0DF9A4@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=stern@rowland.harvard.edu \
    --cc=utrace-devel@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
Powered by JetHome