From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Alexander Graf <agraf@suse.de>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Carsten Otte <cotte@de.ibm.com>, KVM list <kvm@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: RFC: s390: extension capability for new address space layout
Date: Tue, 20 Sep 2011 15:11:48 +0300 [thread overview]
Message-ID: <4E788304.2050008@redhat.com> (raw)
In-Reply-To: <4E787F7A.2070600@de.ibm.com>
On 09/20/2011 02:56 PM, Christian Borntraeger wrote:
> Avi,Marcelo,
>
> 598841ca9919d008b520114d8a4378c4ce4e40a1 ([S390] use gmap address
> spaces for kvm guest images) changed kvm on s390 to use a separate
> address space for kvm guests. We can now put KVM guests anywhere
> in the user address mode with a size up to 8PB - as long as the
> memory is 1MB-aligned. This change was done without KVM extension
> capability bit.
> The change was added after 3.0, but we still have a chance to add
> a feature bit before 3.1 (keeping the releases in a sane state).
>
> Can you have a look at the change below and give you ACK or NACK?
> If ok, I would push this patch to Heiko to be submitted via the
> s390 stream for 3.1.
ACK, with Alex's changes. Why are kvm changes not going in through the
kvm tree? Or at least kvm@ review?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-20 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 11:56 RFC: s390: extension capability for new address space layout Christian Borntraeger
2011-09-20 12:00 ` Alexander Graf
2011-09-20 12:10 ` Christian Borntraeger
2011-09-20 12:11 ` Avi Kivity [this message]
2011-09-20 14:31 ` Carsten Otte
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=4E788304.2050008@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cotte@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 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.