From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org
Subject: Re: [BUG] GPF on hardware breakpoints (preempt_notifier)
Date: Sun, 09 Sep 2007 20:30:01 +0300 [thread overview]
Message-ID: <46E42D99.6030905@qumranet.com> (raw)
In-Reply-To: <20070909171422.GA13345-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
Luca Tettamanti wrote:
> Hi,
> while debugging a program with GDB I got a GPF which seems related to
> KVM. Note that I was *not* using the debugger inside the guest nor on
> the virtual machine. The target was an unrelated userspace program.
>
>
Yes, kvm is dirtily misappropriating the debug registers on older
kernels. We really should context switch them more carefully.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-09 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 17:14 [BUG] GPF on hardware breakpoints (preempt_notifier) Luca Tettamanti
[not found] ` <20070909171422.GA13345-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2007-09-09 17:30 ` Avi Kivity [this message]
[not found] ` <46E42D99.6030905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-09 18:45 ` Luca
[not found] ` <68676e00709091145p34fad472u5cf3e1d939754367-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-09 20:14 ` Anthony Liguori
[not found] ` <46E4542F.8040705-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-09 20:23 ` Luca
[not found] ` <68676e00709091323r23c59dch3f75177616b3f7f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-09 20:43 ` Anthony Liguori
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=46E42D99.6030905@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-TtF/mJH4Jtrk1uMJSBkQmQ@public.gmane.org \
/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