public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Casey Jeffery <kcjeffery-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM and Perf Counters
Date: Thu, 01 Feb 2007 18:15:13 +0200	[thread overview]
Message-ID: <45C21211.3050509@qumranet.com> (raw)
In-Reply-To: <cb6aceaa0702010743v7fba298y23e825ef1e706801-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Casey Jeffery wrote:
> 1. What is the best way to start and ID multiple guests? I've just
> been configuring a script to start up two of them from the
> command-line and storing an ID in the kvm_vcpu structure. The first to
> get to get to vmc_run() is designated as the primary and the other is
> then the secondary that will replicate what the primary does. 

You already have a guest ID -- the pid of the process which created the 
VM.  Is there any reason to have another ID?


> I'm open
> to ideas on automating the creation of multiple guests (with pinning
> to CPUs).
>   

You can pin using taskset(1) or sched_setaffinity(2).  I don't 
understand the problem with automating guest creation.


> 2. Where should the bulk of the buffering and synchronization be done?
> I've been putting everything in the hypervisor since it can see all
> the guests. It may make sense to put some things in the qemu code and
> make use of other IPC mechanisms for synchronization, though.
>   

Userspace is the best place.

> 3. What is the best way to deal with I/O string/string_down calls that
> handle the I/O in kvmctl.c? I would guess it will be necessary to
> buffer the memory range somewhere and pass the address of that someone
> for the secondary guest to access when it gets to that point.
>   

I'd suggest serializing everything over a socket.  That way you can run 
the primary and backup on different machines.

> 4. DMA? I haven't thought about this much yet and am using simple
> guests that don't do it. It will need to be handled eventually,
> though.
>   

Since DMA is handled by qemu, you already have a sync point.  Just tag 
the guest address and data with that sync point.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  parent reply	other threads:[~2007-02-01 16:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10  1:26 KVM and Perf Counters Casey Jeffery
     [not found] ` <cb6aceaa0701091726h7fe94bb3q73db49e43ff226ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-01-10  9:37   ` Avi Kivity
     [not found]     ` <45A4B3E4.7090202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-01 15:43       ` Casey Jeffery
     [not found]         ` <cb6aceaa0702010743v7fba298y23e825ef1e706801-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-02-01 16:10           ` Dor Laor
     [not found]             ` <64F9B87B6B770947A9F8391472E032160A3F2298-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-02-01 17:44               ` Casey Jeffery
2007-02-01 16:15           ` Avi Kivity [this message]
     [not found]             ` <45C21211.3050509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-01 19:28               ` Casey Jeffery

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=45C21211.3050509@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kcjeffery-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-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