From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [PATCH 0 of 2] Refactor vcpu creation path.
Date: Wed, 31 Oct 2007 17:57:27 -0500 [thread overview]
Message-ID: <patchbomb.1193871447@basalt> (raw)
These patches are not simple code movement, and I haven't yet tested them so
I'm just putting them out for comment.
Basically we're expanding the VCPU creation path to add an "arch" layer between
main.c and svm/vmx.c. Since there is one call in each direction (main.c ->
svm/vmx.c, svm/vmx.c -> main.c) we end up with two new architecture functions
in the middle.
5 files changed, 108 insertions(+), 59 deletions(-)
drivers/kvm/kvm.h | 6 +++
drivers/kvm/kvm_main.c | 59 +++----------------------------
drivers/kvm/svm.c | 6 +--
drivers/kvm/vmx.c | 6 +--
drivers/kvm/x86.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++++
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-31 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 22:57 Hollis Blanchard [this message]
2007-10-31 22:57 ` [PATCH 1 of 2] RFC: Create kvm_x86_vcpu_init() Hollis Blanchard
2007-10-31 22:57 ` [PATCH 2 of 2] RFC: Create kvm_arch_vcpu_create() Hollis Blanchard
2007-11-01 13:20 ` [PATCH 0 of 2] Refactor vcpu creation path Avi Kivity
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=patchbomb.1193871447@basalt \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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