kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 2/5] KVM: New guest debug interface
Date: Mon, 08 Dec 2008 10:13:42 +0100	[thread overview]
Message-ID: <493CE546.2030507@siemens.com> (raw)
In-Reply-To: <493B9DAE.7050007@redhat.com>

Avi Kivity wrote:
> Jan Kiszka wrote:
>> This rips out the support for KVM_DEBUG_GUEST and introduces a new IOCTL
>> instead: KVM_SET_GUEST_DEBUG. The IOCTL payload consists of a generic
>> part, controlling the "main switch" and the single-step feature. The
>> arch specific part adds an x86 interface for intercepting both types of
>> debug exceptions separately and re-injecting them when the host was not
>> interested. Moveover, the foundation for guest debugging via debug
>> registers is layed.
>>   
> 
> Have you tested compile-time compatibility with older userspace?

Yes, works.

> 
>> Note that both SVM and VTX are supported, but only the latter was tested
>> yet. Based on the experience with all those VTX corner case, I would be
>> fairly surprised if SVM will work out of the box.
>>
>>   
> 
> I'd like svm to work before applying.

To validate the design?

I will see if I can organize an SVM box, but I can't promise when I'll
be able to do the testing. Anyone willing to contribute time on this
would be warmly welcome!

> 
>> @@ -439,7 +437,8 @@ struct kvm_trace_rec {
>>  #define KVM_SET_SREGS             _IOW(KVMIO,  0x84, struct kvm_sregs)
>>  #define KVM_TRANSLATE             _IOWR(KVMIO, 0x85, struct
>> kvm_translation)
>>  #define KVM_INTERRUPT             _IOW(KVMIO,  0x86, struct
>> kvm_interrupt)
>> -#define KVM_DEBUG_GUEST           _IOW(KVMIO,  0x87, struct
>> kvm_debug_guest)
>> +/* KVM_DEBUG_GUEST is no longer supported, use KVM_SET_GUEST_DEBUG
>> instead */
>> +#define KVM_DEBUG_GUEST           __KVM_DEPRECATED_DEBUG_GUEST
>>  #define KVM_GET_MSRS              _IOWR(KVMIO, 0x88, struct kvm_msrs)
>>  #define KVM_SET_MSRS              _IOW(KVMIO,  0x89, struct kvm_msrs)
>>  #define KVM_SET_CPUID             _IOW(KVMIO,  0x8a, struct kvm_cpuid)
>> @@ -468,6 +467,26 @@ struct kvm_trace_rec {
>>  #define KVM_SET_MP_STATE          _IOW(KVMIO,  0x99, struct
>> kvm_mp_state)
>>  /* Available with KVM_CAP_NMI */
>>  #define KVM_NMI                   _IO(KVMIO,  0x9a)
>> +/* Available with KVM_CAP_SET_GUEST_DEBUG */
>> +#define KVM_SET_GUEST_DEBUG       _IOW(KVMIO,  0x9a, struct
>> kvm_guest_debug)
>> +
>>   
> 
> 0x9b...

Oh, rebased a bit too often.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux

  reply	other threads:[~2008-12-08  9:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 11:43 [PATCH 0/5] KVM: Improved guest debugging / debug register emulation Jan Kiszka
2008-11-27 11:43 ` [PATCH 2/5] KVM: New guest debug interface Jan Kiszka
2008-12-07  9:55   ` Avi Kivity
2008-12-08  9:13     ` Jan Kiszka [this message]
2008-12-08  9:34       ` Avi Kivity
2008-12-08  9:42         ` Jan Kiszka
2008-12-08 13:47         ` Jan Kiszka
2008-12-08 14:57           ` Avi Kivity
2008-12-08 15:17             ` Jan Kiszka
2008-12-10  8:48               ` Avi Kivity
2008-11-27 11:43 ` [PATCH 1/5] VMX: Support for injecting software exceptions Jan Kiszka
2008-11-27 11:43 ` [PATCH 4/5] KVM: x86: Virtualize debug registers Jan Kiszka
2008-11-27 11:43 ` [PATCH 3/5] KVM: VMX: Ensure interruptibility when single-stepping Jan Kiszka
2008-12-07 10:05   ` Avi Kivity
2008-12-08  9:17     ` Jan Kiszka
2008-12-11 19:15     ` [PATCH] KVM: VMX: Allow single-stepping when interruptible Jan Kiszka
2008-11-27 11:43 ` [PATCH 5/5] KVM: x86: Wire-up hardware breakpoints for guest debugging Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2008-10-06  9:15 [PATCH 0/5] KVM: Fix and improve guest debugging and x86 debug registers Jan Kiszka
2008-10-06  9:15 ` [PATCH 2/5] KVM: New guest debug interface 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=493CE546.2030507@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@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;
as well as URLs for NNTP newsgroup(s).