From: Jerone Young <jyoung5@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] [v5] Add gdb break point support to PowerPC kvm
Date: Tue, 10 Jun 2008 16:27:51 +0000 [thread overview]
Message-ID: <1213115271.21743.3.camel@thinkpadL> (raw)
In-Reply-To: <1664758e846c292f5882.1213035589@thinkpadL>
On Tue, 2008-06-10 at 10:45 -0500, Hollis Blanchard wrote:
> On Tue, 2008-06-10 at 10:33 -0500, Jerone Young wrote:
> > On Tue, 2008-06-10 at 10:12 -0500, Hollis Blanchard wrote:
> > > On Mon, 2008-06-09 at 18:56 -0500, Jerone Young wrote:
> > > > > > If an IAC is matched before we enter the guest it will be caught host
> > > > > > that catches it.
> > > > >
> > > > > But that won't happen because you've disabled MSR[DE].
> > > >
> > > > Ah... you don't rember the whole imprecise interrupts ;-) . When MSR[DE]
> > > > =0 and an IAC will go off but not at the exact address. This was fun
> > > > figuring out.
> > >
> > > Right. Now, when will the deferred debug event fire, and who will handle
> > > it? What can we do about that?
> >
> > If the debug registers are turned off before we disable MSR[DE], there
> > will be no debug events at all.
> >
> > This is what I was talking about in my first couple of emails. If a
> > debug event does go off and the host does not handle it, the only way to
> > know is the dbsr register (and there is no way to save that off). So in
> > the end it could end up going off in the guest.
> >
> > This is why I said you should not do host debugging if you want to do
> > guest debugging at the sametime, as a work around for now.
>
> As I said before, forget host debugging!
>
> In fact, here is the exact text I sent to you on Friday, which you don't
> appear to have read, in which I said exactly the same thing:
>
> On Fri, 2008-06-06 at 14:27 -0500, Hollis Blanchard wrote:
> > On Fri, 2008-06-06 at 14:11 -0500, Jerone Young wrote:
> > > That is an issue if you are using the IAC registers in the host
> > also > at the same time.
> >
> > That is a totally separate issue. Imagine this in the host:
> >
> > 0xc0001000 load_guest_debug_registers:
> > MSR[DE] = 0
> > IAC[0] = 0xc0001080
> > ...
> > 0xc0001080
> > ...
> > enter guest
> >
> > IAC1 matched. Now what happens?
>
> Please think about this scenario.
Oh it hit me. So we *could* get an imprecise interrupt once we enable
dbcr0.
So do you want to enable dbcr0 once we enable MSR_DE in
__kvmppc_vcpu_run() ?
(In the future please just plainly state the issue..it saves
emails..which I guess saves trees .. in someway).
>
> > I can clear the dbsr registers also when disabling the debug interrupts
> > as a solution?
>
> I think you're on the right track, but what you propose here simply
> won't affect the above scenario.
>
prev parent reply other threads:[~2008-06-10 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 18:19 [PATCH] [v5] Add gdb break point support to PowerPC kvm Jerone Young
2008-06-09 20:51 ` Hollis Blanchard
2008-06-09 21:08 ` Jerone Young
2008-06-09 22:56 ` Hollis Blanchard
2008-06-09 23:56 ` Jerone Young
2008-06-10 15:12 ` Hollis Blanchard
2008-06-10 15:33 ` Jerone Young
2008-06-10 15:45 ` Hollis Blanchard
2008-06-10 15:54 ` Jerone Young
2008-06-10 16:27 ` Jerone Young [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=1213115271.21743.3.camel@thinkpadL \
--to=jyoung5@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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