public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Brandon Dwiel <bhdwiel@ncsu.edu>
To: kvm@vger.kernel.org
Subject: Helping with KVM development
Date: Fri, 15 Feb 2013 14:27:35 -0500	[thread overview]
Message-ID: <511E8C27.7060504@ncsu.edu> (raw)

Hi,

I'm a computer engineering PhD student and I have the opportunity to
contribute something to KVM as a class project. I found a few
interesting items on the KVM TODO list (http://www.linux-kvm.org/page/TODO)
that I could do. If I choose to do
this I would start immediately and have about 2 months to finish. I
wouldn't choose this project if I thought I would have to rely on the
help of you guys, but I think my biggest challenge will be diving in and
getting started. Hopefully you can help with that.

My focus is on computer architecture so the x86 topics really interested
me. Here are the specific ones that I think I could do. I would start by
implementing one, and if that ends up not being substantial enough for a
final project, I'd do another.

1. Improve mmu page eviction algorithm (currently FIFO, change to
approximate LRU).
2. On-demand register access, really, copying all registers all the
time is gross.
3. Implement mmx and sse memory move instructions; useful for guests
that use multimedia extensions for accessing vga (partially done)
4. Implement an operation queue for the emulator. The emulator often
calls userspace to perform a read or a write, but due to inversion
of control it actually restarts instead of continuing. The queue
would allow it to replay all previous operations until it reaches
the point it last stopped.
5. convert more instructions to direct dispatch (function pointer in
decode table)
6. move init_emulate_ctxt() into x86_decode_insn() and other emulator
entry points

Have any of these already been implemented? It seems number 2 and
possibly 1 already have been. I think this list is quite outdated, so is
there something else along these lines of these updates that I could
help with?

Thanks,
Brandon

             reply	other threads:[~2013-02-15 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 19:27 Brandon Dwiel [this message]
2013-02-19 13:01 ` Helping with KVM development Gleb Natapov

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=511E8C27.7060504@ncsu.edu \
    --to=bhdwiel@ncsu.edu \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox