From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Use thread debug register storage instead of kvm specific data
Date: Tue, 01 Sep 2009 15:27:48 +0300 [thread overview]
Message-ID: <4A9D1344.5080401@redhat.com> (raw)
In-Reply-To: <4A9D0D59.9020406@redhat.com>
On 09/01/2009 03:02 PM, Avi Kivity wrote:
>> Then we need to resolve it right from the start, not in some distant
>> future. We already have everything we need available, we could just try
>> to refactor it to a nicer interface (something that encapsulates both
>> compile and runtime tests).
>
>
> I'll look at doing something. It shouldn't be difficult.
>
btw, it looks like kgdb is already broken wrt prtace hardware breakpoints.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-01 12:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 9:44 [PATCH] KVM: Use thread debug register storage instead of kvm specific data Avi Kivity
2009-09-01 9:47 ` Avi Kivity
2009-09-01 18:12 ` Andrew Theurer
2009-09-01 18:23 ` Avi Kivity
2009-09-04 14:48 ` Andrew Theurer
2009-09-04 15:30 ` Brian Jackson
2009-09-04 16:08 ` Andrew Theurer
2009-09-04 17:04 ` Brian Jackson
2009-09-05 11:34 ` Vadim Rozenfeld
2009-09-06 12:49 ` Yan Vugenfirer
2009-09-06 8:21 ` Avi Kivity
2009-09-01 10:42 ` Jan Kiszka
2009-09-01 11:08 ` Jan Kiszka
2009-09-01 11:16 ` Avi Kivity
2009-09-01 11:21 ` Avi Kivity
2009-09-01 13:31 ` Jan Kiszka
2009-09-01 13:39 ` Avi Kivity
2009-09-01 11:22 ` Marcelo Tosatti
2009-09-01 11:28 ` Jan Kiszka
2009-09-01 11:32 ` Marcelo Tosatti
2009-09-01 11:35 ` Avi Kivity
2009-09-01 11:33 ` Jan Kiszka
2009-09-01 11:43 ` Avi Kivity
2009-09-01 11:45 ` Jan Kiszka
2009-09-01 11:56 ` Avi Kivity
2009-09-01 12:01 ` Jan Kiszka
2009-09-01 12:02 ` Avi Kivity
2009-09-01 12:27 ` Avi Kivity [this message]
2009-09-01 11:34 ` Avi Kivity
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=4A9D1344.5080401@redhat.com \
--to=avi@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.