All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: kernel status update
Date: Fri, 31 Oct 2008 19:44:08 +0000	[thread overview]
Message-ID: <1225482248.14521.22.camel@localhost.localdomain> (raw)

I've posted most of the patches here before, but I've built up a small
backlog of patches to be pushed upstream. I've been running with them
long enough to be happy with them, and I've just posted them all to
http://penguinppc.org/~hollisb/kvm/patches/

There are two really minor patches I want to have acked by the PPC
maintainers before I push the whole series to Avi, however. I've
submitted those for review already, so hopefully that will be done by
early next week.

This patch series has two main components, refactoring and optimization:
      * It dramatically restructures some of the code flow and data
        structures to make supporting other processors possible. There
        are still a few rough corners though, like the TLB miss handling
        in booke.c kvmppc_handle_exit(). At this point I'd be OK with
        duplicating those handlers into core-specific files.
      * Based on Christian's analysis and patches, there is some
        performance optimization for Book E and 440 code.
      * Yu's idea about TLB handling was great, and I saw about a 20%
        performance improvement on a couple small workloads on 440. Very
        happy about that one. :)

Anyways, just an update to let folks know where things sit on the kernel
side.

-- 
Hollis Blanchard
IBM Linux Technology Center


             reply	other threads:[~2008-10-31 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 19:44 Hollis Blanchard [this message]
2008-11-03  1:58 ` kernel status update Liu Yu
2008-11-07  0:40 ` 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=1225482248.14521.22.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.