From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: Update instruction length on intercepted BP
Date: Wed, 17 Feb 2010 13:11:36 +0200 [thread overview]
Message-ID: <4B7BCEE8.8040708@redhat.com> (raw)
In-Reply-To: <20100215133042.GC19478@redhat.com>
On 02/15/2010 03:30 PM, Gleb Natapov wrote:
>
>> I just did this on our primary AMD platform (Embedded Opteron, 13KS EE),
>> and it just worked.
>>
>> But this is a fairly new processor. Consequently, it reports NextRIP
>> support via cpuid function 0x8000000A. Looking for an older one too.
>>
>> In the meantime I also browsed a bit more in the manuals, and I don't
>> think stepping over or (what is actually required) into an INT3 will
>> work. We can't step into as the processor clears TF on any event handler
>> entry. And stepping over would cause troubles
>>
>> a) as an unknown amount of code may run without #DB interception
>> b) we would fiddle with TF in code that is already under debugger
>> control, thus we would very likely run into conflicts.
>>
>> Leaves us with tricky INT3 emulation. Sigh.
>>
>>
> So the question is do we want to support this kind of debugging on older
> AMDs. May we don't.
>
How much older are they?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-17 11:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 9:31 [PATCH] KVM: VMX: Update instruction length on intercepted BP Jan Kiszka
2010-02-14 7:53 ` Gleb Natapov
2010-02-14 10:26 ` Jan Kiszka
2010-02-14 10:34 ` Gleb Natapov
2010-02-14 10:47 ` Jan Kiszka
2010-02-14 11:15 ` Gleb Natapov
2010-02-14 11:39 ` Jan Kiszka
2010-02-14 14:16 ` Avi Kivity
2010-02-14 16:38 ` Jan Kiszka
2010-02-14 16:44 ` Avi Kivity
2010-02-14 17:06 ` Jan Kiszka
2010-02-15 6:48 ` Avi Kivity
2010-02-14 14:45 ` Gleb Natapov
2010-02-14 16:37 ` Jan Kiszka
2010-02-14 16:53 ` Gleb Natapov
2010-02-14 17:06 ` Jan Kiszka
2010-02-14 17:26 ` Gleb Natapov
2010-02-14 17:49 ` Jan Kiszka
2010-02-15 13:20 ` Jan Kiszka
2010-02-15 13:30 ` Gleb Natapov
2010-02-15 14:25 ` Jan Kiszka
2010-02-17 11:11 ` Avi Kivity [this message]
2010-02-17 11:13 ` Gleb Natapov
2010-02-17 11:24 ` Jan Kiszka
2010-02-17 12:39 ` Gleb Natapov
2010-02-17 10:55 ` Gleb Natapov
2010-02-17 11:32 ` Jan Kiszka
2010-02-17 13:03 ` Gleb Natapov
2010-02-17 15:13 ` Jan Kiszka
2010-02-17 16:11 ` Gleb Natapov
2010-02-16 11:20 ` Gleb Natapov
2010-02-16 11:25 ` Gleb Natapov
2010-02-14 12:27 ` Avi Kivity
2010-02-14 12:39 ` Jan Kiszka
2010-02-14 12:43 ` Gleb Natapov
2010-02-14 12:47 ` Avi Kivity
2010-02-14 12:53 ` Gleb Natapov
2010-02-14 13:23 ` Jan Kiszka
2010-02-14 13:29 ` 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=4B7BCEE8.8040708@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 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.