public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Working on an entry-level project
Date: Sat, 13 Oct 2007 12:39:15 +0200	[thread overview]
Message-ID: <4710A053.4030400@qumranet.com> (raw)
In-Reply-To: <470FCB69.1050105-edFDblaTWIyXbbII50Afww@public.gmane.org>

Cam Macdonell wrote:
> Dor Laor wrote:
>> Cam Macdonell wrote:
>>>
>> It's a simple test, when there are keyboard/mouse/display changes 
>> keep the refresh rate high. When there are no changes start decrease 
>> the rate until a minimum
>> reached. The performance benefit should also be checked since if it 
>> minimal there's no use for this optimization.
>>> Related to that, what is the status of VMGL's 
>>> (http://www.cs.toronto.edu/~andreslc/xen-gl/) integration with KVM 
>>> or QEMU?  Has anyone tried it?  I've found some pages that refer to 
>>> QEMU and VMGL but nothing definitive.
>>>
>> Go ahead, there claim it can work with qemu. Try first with qemu 
>> since it is the repository to contribute the code to.
>> KVM will inherit it from qemu.
>
> Is there a way to test with QEMU that is not painfully slow?
>
> Cam
maybe using kqemu,
i guess you can work on kvm, if you keep checking that it still work on 
qemu.


-------------------------------------------------------------------------
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/

  parent reply	other threads:[~2007-10-13 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 16:07 Working on an entry-level project Cam Macdonell
     [not found] ` <470CF8B2.4070104-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-10 16:05   ` Izik Eidus
     [not found]     ` <470CF853.5030502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-10 16:52       ` Cam Macdonell
     [not found]         ` <470D0359.5030607-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-11  8:40           ` Dor Laor
     [not found]             ` <470DE190.7070701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 16:07               ` Cam Macdonell
     [not found]                 ` <470E4A55.807-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-12 10:07                   ` Dor Laor
     [not found]                     ` <470F477E.4060302-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-12 19:30                       ` Cam Macdonell
     [not found]                         ` <470FCB69.1050105-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-10-13 10:39                           ` Izik Eidus [this message]
     [not found]                             ` <4710A053.4030400-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-13 21:16                               ` Jindrich Makovicka
     [not found]                                 ` <47137A47.9010505@cs.ualberta.ca>
     [not found]                                   ` <20071015185341.09a732b2@holly>
2007-10-31 18:18                                     ` Cam Macdonell

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=4710A053.4030400@qumranet.com \
    --to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=cam-edFDblaTWIyXbbII50Afww@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