public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: avi@redhat.com
Cc: chrisw@sous-sol.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [KVM PATCH v2 0/3] mmio/pio cleanup
Date: Wed, 27 May 2009 17:37:34 -0400	[thread overview]
Message-ID: <20090527213535.24324.62362.stgit@dev.haskins.net> (raw)

This is v2 of the series, and applies to kvm.git/master:1a6a35a1)

This is in prep for some more substantial mmio/pio work for iosignalfd,
coming later.

---

Gregory Haskins (3):
      kvm: do not register i8254 PIO regions until we are initialized
      kvm: cleanup io_device code
      kvm: fix potential coalesced_mmio leak on shutdown


 arch/x86/kvm/i8254.c      |   53 +++++++++++++++++++++++++++++----------------
 arch/x86/kvm/i8259.c      |   20 ++++++++++++-----
 arch/x86/kvm/lapic.c      |   22 +++++++++++++------
 arch/x86/kvm/x86.c        |    2 +-
 virt/kvm/coalesced_mmio.c |   26 ++++++++++++++--------
 virt/kvm/ioapic.c         |   22 +++++++++++++------
 virt/kvm/iodev.h          |   25 +++++++++++++++------
 virt/kvm/kvm_main.c       |    2 +-
 8 files changed, 115 insertions(+), 57 deletions(-)

-- 
Signature

             reply	other threads:[~2009-05-27 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 21:37 Gregory Haskins [this message]
2009-05-27 21:37 ` [KVM PATCH v2 1/3] kvm: fix potential coalesced_mmio leak on shutdown Gregory Haskins
2009-05-27 21:37 ` [KVM PATCH v2 2/3] kvm: cleanup io_device code Gregory Haskins
2009-05-28  5:49   ` Chris Wright
2009-05-28 11:59     ` Gregory Haskins
2009-05-27 21:37 ` [KVM PATCH v2 3/3] kvm: do not register i8254 PIO regions until we are initialized Gregory Haskins
2009-05-31 10:14 ` [KVM PATCH v2 0/3] mmio/pio cleanup 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=20090527213535.24324.62362.stgit@dev.haskins.net \
    --to=ghaskins@novell.com \
    --cc=avi@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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