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 14:43:03 +0300 [thread overview]
Message-ID: <4A9D08C7.2070206@redhat.com> (raw)
In-Reply-To: <4A9D0678.5040800@siemens.com>
On 09/01/2009 02:33 PM, Jan Kiszka wrote:
> For the time being, falling back to conservative save/restore if kgdb is
> configured in and kgdb_connected != 0 should allow us to apply this
> optimization otherwise.
>
I prefer a real fix instead of spaghettiing the code this way (and in
the meanwhile I'm fine with kgdb hardware breakpoints not working while
kvm is running).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-01 11:43 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 [this message]
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
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=4A9D08C7.2070206@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 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).