All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org, Craig Brozefsky <craig@red-bean.com>
Subject: Re: [Qemu-devel] Re: software breakpoints disappearing/reappearing in	KVM/qemu
Date: Sun, 10 Apr 2011 17:41:24 +0300	[thread overview]
Message-ID: <4DA1C194.2000005@redhat.com> (raw)
In-Reply-To: <4DA1BD64.6000108@web.de>

On 04/10/2011 05:23 PM, Jan Kiszka wrote:
> On 2011-04-10 16:01, Avi Kivity wrote:
> >  On 04/08/2011 11:52 PM, Jan Kiszka wrote:
> >>  QEMU's gdbstub in KVM mode is simply not designed to account for guests
> >>  swapping out code pages that contain breakpoints. Due to the fact that
> >>  the Linux kernel does not do these weird things to its own code,
> >
> >  It actually happily patches its own code at certain circumstances.  If
> >  you debug early boot or suspend/resume or cpu hotplug you're likely to
> >  encounter them.
>
> Yes, it patches (alternates, jump_labels, mcount etc.), but it doesn't
> swap or move code pages. At least so far.
>

Try using modules (though that's different - the virtual addresses will 
change too).  Or debugging a mixed kernel/user workload.

> If you need to break at such locations, there are still hardware
> breakpoints, though only 4.

Right.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-04-10 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 18:50 [Qemu-devel] software breakpoints disappearing/reappearing in KVM/qemu Craig Brozefsky
2011-04-08 20:16 ` Blue Swirl
2011-04-08 20:37   ` Craig Brozefsky
2011-04-08 20:52 ` [Qemu-devel] " Jan Kiszka
2011-04-10 14:01   ` Avi Kivity
2011-04-10 14:23     ` Jan Kiszka
2011-04-10 14:41       ` Avi Kivity [this message]
2011-04-10 15:16         ` Jan Kiszka

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=4DA1C194.2000005@redhat.com \
    --to=avi@redhat.com \
    --cc=craig@red-bean.com \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.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 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.