From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Lucas Meneghel Rodrigues <lmr@redhat.com>
Subject: Re: [PATCH] KVM: VMX: Update instruction length on intercepted BP
Date: Sun, 14 Feb 2010 18:06:40 +0100 [thread overview]
Message-ID: <4B782DA0.5030301@web.de> (raw)
In-Reply-To: <4B78286F.4000103@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Avi Kivity wrote:
> On 02/14/2010 06:38 PM, Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> On 02/14/2010 01:39 PM, Jan Kiszka wrote:
>>>
>>>>> that will work for both VMX and SVM before applying patches that make
>>>>> oly VMX work?
>>>>>
>>>>>
>>>> VMX used to work, so my patch is actually a regression fix. I bet this
>>>> was accidentally broken while cleaning up the interrupt handling of
>>>> VMX.
>>>>
>>>>
>>>>
>>> Care to post a test case?
>>>
>>> I can't say we run the internal test suite at the moment, but it should
>>> really be integrated into autotest.
>>>
>>>
>> I know this should have been done long before. I just haven't worked on
>> autotest so far (a colleague did, though), so there is some reluctance
>> to get wet feet. But maybe I find some rubber boots.
>>
>
> The autotest people (Lucas copied) are generally good at adding tests,
> so all we need to do is (a) add a test case to
> qemu-kvm.git:kvm/user/test (b) indicate to the autotest people how to
> build and run this thing.
I wonder if it requires a stand-alone test. So far I'm testing the guest
side via gdb installed in some Linux image. We need to interact with gdb
anyway to test guest debugging, so this would just add another instance
and some indirection (via serial console or ssh into the guest).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-02-14 17:07 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 [this message]
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
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=4B782DA0.5030301@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox