qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for June 8
Date: Tue, 8 Jun 2010 08:05:00 -0700	[thread overview]
Message-ID: <20100608150500.GA28492@x200.localdomain> (raw)

Accelerating counters (aka moving PIT to userspace, keeping HPET in
userspace)
- PIT (in-kernel, userspace, or split)
- userspace PIT, too slow
- kernel PIT (already seen bugs)
- split PIT, not realistic w/out a sane interface (see bugs above)
- exit to userspace is a base cost, add MSR save/restore, add qemu
  overhead...and exit to userspace is expensive
- hpet in userspace (at least minimal counter reading)
- ioapic 
  - less than half is architectural, more than half endds of being
     interrupt reinjection

Live migration + hotplug
- start a machine, hotplug device, allocate ram...can't migrate
  - last_offset and ramblock sections coming from cmdline may not be
    compatible w/ hotplug
  - worst case is different ramblock order and data corruption
- alex has patches to convert ramblocks into queuelist
  - give name, offset
  - will clean up and send out today

migration events?
- QMP (wire protocol) has nice async events
  - QError reasonable
  - migration is async command, can complete w/ error or success
- QMP broken for error
  - need context for error, default is monitor, but async command
  - redo qerror_report, propagate error (or always have error context
    available)
- monitor and qmp done w/ same dispatch functions
  - should do monitor in terms of qmp
    - every qerror replacing monitor printf error
      - ends up not sharing enough ($foo not found, where $foo is contextual)
- async command (pass in command completion)
- may have to do limited (throw away for 0.13 and redo properly for 0.14)
- anthony has a (not fully working) tree, and will document direction on wiki

migration subsections.
- stable IDE version 3 is different for <= 0.12.2  than > 0.12.2
- for stable could bump to version 4, blacklist version 3
- unstable IDE version 4, works

APIC wiring problems (attached slides)
- postponed until tomorrow's code overview slot

             reply	other threads:[~2010-06-08 15:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 15:05 Chris Wright [this message]
2010-06-08 16:01 ` [Qemu-devel] Re: KVM call minutes for June 8 Anthony Liguori
2010-06-08 20:59   ` Luiz Capitulino
2010-06-08 21:13     ` Anthony Liguori
2010-06-09 15:18       ` Luiz Capitulino
2010-06-09 15:31         ` Daniel P. Berrange
2010-06-09 16:22           ` Anthony Liguori
2010-06-09 16:29             ` Daniel P. Berrange
2010-06-10  9:43             ` Kevin Wolf
2010-06-10 12:53               ` Anthony Liguori
2010-06-10 13:08                 ` Kevin Wolf
2010-06-10 14:11                   ` Avi Kivity
2010-06-10 14:22                     ` Kevin Wolf
2010-06-10 14:27                   ` Anthony Liguori
2010-06-11 12:55                     ` Luiz Capitulino
2010-06-11 13:48                       ` Anthony Liguori
2010-06-09 16:26         ` Anthony Liguori

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=20100608150500.GA28492@x200.localdomain \
    --to=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).