From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/11] Add E500 support in KVM
Date: Tue, 16 Dec 2008 01:41:53 +0000 [thread overview]
Message-ID: <1229391713.4313.60.camel@localhost.localdomain> (raw)
In-Reply-To: <1228986705-9213-1-git-send-email-yu.liu@freescale.com>
On Thu, 2008-12-11 at 17:11 +0800, Liu Yu wrote:
> This patch set add E500 support in KVM,
> and is already based on Hollis's feedback (a patchset which not yet commit)
I'm fairly happy with this series, aside from the mostly minor comments
I've made so far. It's definitely a plus that you've managed not to
break 440 while writing this code, congratulations. :) If you're able to
revise them, I think we can commit these patches this week.
By the way, have you looked into reserving enough host memory to use
large pages for the guest kernel mapping? That will be critical to
getting good performance.
Also, do you have any qemu patches?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-12-16 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 9:11 [PATCH 0/11] Add E500 support in KVM Liu Yu
2008-12-11 18:24 ` Hollis Blanchard
2008-12-16 1:41 ` Hollis Blanchard [this message]
2008-12-16 10:25 ` Liu Yu
2008-12-16 22:53 ` Hollis Blanchard
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=1229391713.4313.60.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
/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.