From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Fix srcu struct leakage
Date: Tue, 09 Nov 2010 18:00:51 +0200 [thread overview]
Message-ID: <4CD97033.9090805@redhat.com> (raw)
In-Reply-To: <4CD95C88.2000904@siemens.com>
On 11/09/2010 04:36 PM, Jan Kiszka wrote:
>
>> and have ia64 provide its special stuff. The practice of duplicating
>> common code just because of one outlier is bad, there are better ways.
>>
>> (and I will accept untested ia64 patches provided kvm-ia64@ is copied).
> OK, will come. Refactoring will affect all archs, so all need to test
> and ack.
I can at least build on all of them. Should set up a buildbot...
next prev parent reply other threads:[~2010-11-09 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 11:41 [PATCH] KVM: Fix srcu struct leakage Jan Kiszka
2010-11-09 13:30 ` Avi Kivity
2010-11-09 13:53 ` Marcelo Tosatti
2010-11-09 13:59 ` Jan Kiszka
2010-11-09 14:03 ` Marcelo Tosatti
2010-11-09 14:07 ` Jan Kiszka
2010-11-09 14:30 ` Avi Kivity
2010-11-09 14:36 ` Jan Kiszka
2010-11-09 16:00 ` Avi Kivity [this message]
2010-11-09 14:05 ` Jan Kiszka
2010-11-09 14:00 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2010-11-07 12:58 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=4CD97033.9090805@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