From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [00/03][PATCH] kvm-ia64 updates for linux-2.6.28-rc2
Date: Wed, 29 Oct 2008 16:45:10 +0200 [thread overview]
Message-ID: <490876F6.7070009@redhat.com> (raw)
In-Reply-To: <yq0tzavfp2t.fsf@jaguar.mkp.net>
Jes Sorensen wrote:
> Avi> Applied all, thanks. Is the third patch needed for 2.6.28? What
> Avi> scenario does it fix?
>
> Please!
>
> The third patch reorganizes the data structures which saves us a ton
> of space so we can go from 8 to 60 vcpus .... Would like it in as I
> have stuff that I want to fix that goes on top of this.
>
>
No, that's the first patch. And it was applied, but for 2.6.29, not 2.6.28.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-29 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 4:39 [00/03][PATCH] kvm-ia64 updates for linux-2.6.28-rc2 Zhang, Xiantao
2008-10-29 14:27 ` Avi Kivity
2008-10-29 14:33 ` Jes Sorensen
2008-10-29 14:45 ` Avi Kivity [this message]
2008-10-29 14:51 ` Jes Sorensen
2008-10-30 1:05 ` Zhang, Xiantao
2008-10-30 9:36 ` Avi Kivity
2008-10-30 10:16 ` Zhang, Xiantao
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=490876F6.7070009@redhat.com \
--to=avi@redhat.com \
--cc=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@intel.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