From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
KVM list <kvm@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [RFC/PATCH] kvm: Handle diagnose 0x10 (release pages)
Date: Sun, 16 Oct 2011 10:51:07 +0200 [thread overview]
Message-ID: <4E9A9AFB.1040509@redhat.com> (raw)
In-Reply-To: <4E97FB9E.4050804@de.ibm.com>
On 10/14/2011 11:06 AM, Christian Borntraeger wrote:
> Avi, Marcelo,
>
> below is a patch for the System z (s390x) ballooner (as defined by the
> other System z hypervisors). I want to push that patch via Martins tree,
> since the tricky part is in architecture specific memory management code.
>
> Can you ack/nack?
>
Sure:
Acked-by: Avi Kivity <avi@redhat.com>
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-10-16 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 9:06 [RFC/PATCH] kvm: Handle diagnose 0x10 (release pages) Christian Borntraeger
2011-10-16 8:51 ` Avi Kivity [this message]
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=4E9A9AFB.1040509@redhat.com \
--to=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.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).