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 developer call minutes (Feb 2)
Date: Tue, 2 Feb 2010 09:07:26 -0800	[thread overview]
Message-ID: <20100202170726.GC20233@x200.localdomain> (raw)

Minutes (please reply w/ corrections or follow-ups):

state of in-kernel APIC/IOAPIC/PIT upstream merge
- Glauber?...

road map to get rid of qemu-kvm's slot management (IMHO: qemu-kvm-0.13)
- no real feedback here

- any further ongoing/planned upstream merge efforts?
  - SMP
    - needs in-kernel irqchip support upstream
    - possibly make it a stream in uq for integration and autotesting
  - PCI Device Assignment cleanup, proper capabilities support
    - do we move to uio support before pushing upstream?
    - Michael's UIO patch for 2.3 devices is upstream, so moving to uio
      would add a feature
    - what is missing w/out PCIe bus emulation
      - AER, ARI, few other less critical things
    - any 64-bit issues or other things that a driver may probe for that
      will break ww/out PCIe
      - most are probing PCI capabilities

upstream queue uq qemu-kvm 
- flush mmio buffer periodically
- enabled unconditional save/restore
- started porting -mempath
- getting autotest to run on upstream to autotest before sending patches
  to upstream
- anthony wants to receive pull request w/ inline patches for review

qmp feature negotiation issue
- Luiz and Markus discussing alternatives, either seems fine
  - Anthony will follow-up on list

                 reply	other threads:[~2010-02-02 17:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100202170726.GC20233@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).