From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [kvm-devel] [RFC][PATCH 2/4] kvm: Arch-specifc KVM_EXIT_DEBUG payload
Date: Thu, 22 May 2008 17:35:50 +0300 [thread overview]
Message-ID: <483584C6.6080506@qumranet.com> (raw)
In-Reply-To: <483583EF.1010907@web.de>
Jan Kiszka wrote:
> Well, might be useful. But then we would also have to teach this support
> to the gdb remote protocol and the gdb frontend, because neither of both
> seems to make use of it yet. And do other archs have it as well? If at
> all, I guess the way this is realized there varies a lot, and thus
> abstracting it is the real problem.
>
> However, we can keep it in mind for the time the basic feature set works
> perfectly. :)
>
Right, no need to implement it now. But you can reserve some bytes in
the ioctl argument.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-05-22 14:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <482D9198.7040801@web.de>
2008-05-16 16:01 ` [RFC][PATCH 1/4] qemu: refactor cpu_watch/breakpoint API Jan Kiszka
2008-05-16 16:01 ` [RFC][PATCH 2/4] kvm: Arch-specifc KVM_EXIT_DEBUG payload Jan Kiszka
2008-05-21 15:59 ` [kvm-devel] " Avi Kivity
2008-05-22 13:27 ` Jan Kiszka
2008-05-21 16:04 ` Avi Kivity
2008-05-22 13:42 ` Jan Kiszka
2008-05-22 13:59 ` Avi Kivity
2008-05-22 14:32 ` Jan Kiszka
2008-05-22 14:35 ` Avi Kivity [this message]
2008-05-16 16:02 ` [RFC][PATCH 3/4] kvm-vmx: KVM_EXIT_DEBUG on #BP exceptions Jan Kiszka
2008-05-21 16:01 ` [kvm-devel] " Avi Kivity
2008-05-22 13:31 ` Jan Kiszka
2008-05-22 13:58 ` Avi Kivity
2008-05-22 14:24 ` Jan Kiszka
2008-05-22 14:31 ` Avi Kivity
2008-05-22 14:26 ` Hollis Blanchard
2008-05-22 14:34 ` Avi Kivity
2008-05-22 18:27 ` Hollis Blanchard
2008-05-25 10:24 ` Avi Kivity
2008-05-16 16:02 ` [RFC][PATCH 4/4] kvm-userspace: use soft-BPs for guest debugging 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=483584C6.6080506@qumranet.com \
--to=avi@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=jan.kiszka@web.de \
--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 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.