kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@redhat.com>
To: kvm@vger.kernel.org
Cc: avi@redhat.com
Subject: [PATCH] remove leftover:
Date: Wed,  8 Jul 2009 08:34:47 -0400	[thread overview]
Message-ID: <1247056487-26739-1-git-send-email-glommer@redhat.com> (raw)

get rid of kvm_callbacks structure definition

Signed-off-by: Glauber Costa <glommer@redhat.com>
---
 libkvm-all.h |   57 ---------------------------------------------------------
 1 files changed, 0 insertions(+), 57 deletions(-)

diff --git a/libkvm-all.h b/libkvm-all.h
index e16646c..f0d2489 100644
--- a/libkvm-all.h
+++ b/libkvm-all.h
@@ -105,7 +105,6 @@ int handle_io_window(kvm_context_t kvm);
 int handle_debug(kvm_vcpu_context_t vcpu, void *env);
 int try_push_interrupts(kvm_context_t kvm);
 
-
 #if defined(__x86_64__) || defined(__i386__)
 struct kvm_msr_list *kvm_get_msr_list(kvm_context_t);
 int kvm_get_msrs(kvm_vcpu_context_t, struct kvm_msr_entry *msrs, int n);
@@ -113,62 +112,6 @@ int kvm_set_msrs(kvm_vcpu_context_t, struct kvm_msr_entry *msrs, int n);
 #endif
 
 /*!
- * \brief KVM callbacks structure
- *
- * This structure holds pointers to various functions that KVM will call
- * when it encounters something that cannot be virtualized, such as
- * accessing hardware devices via MMIO or regular IO.
- */
-struct kvm_callbacks {
-	/// For 8bit IO reads from the guest (Usually when executing 'inb')
-    int (*inb)(void *opaque, uint16_t addr, uint8_t *data);
-	/// For 16bit IO reads from the guest (Usually when executing 'inw')
-    int (*inw)(void *opaque, uint16_t addr, uint16_t *data);
-	/// For 32bit IO reads from the guest (Usually when executing 'inl')
-    int (*inl)(void *opaque, uint16_t addr, uint32_t *data);
-	/// For 8bit IO writes from the guest (Usually when executing 'outb')
-    int (*outb)(void *opaque, uint16_t addr, uint8_t data);
-	/// For 16bit IO writes from the guest (Usually when executing 'outw')
-    int (*outw)(void *opaque, uint16_t addr, uint16_t data);
-	/// For 32bit IO writes from the guest (Usually when executing 'outl')
-    int (*outl)(void *opaque, uint16_t addr, uint32_t data);
-	/// generic memory reads to unmapped memory (For MMIO devices)
-    int (*mmio_read)(void *opaque, uint64_t addr, uint8_t *data,
-					int len);
-	/// generic memory writes to unmapped memory (For MMIO devices)
-    int (*mmio_write)(void *opaque, uint64_t addr, uint8_t *data,
-					int len);
-#ifdef KVM_CAP_SET_GUEST_DEBUG
-    int (*debug)(void *opaque, void *env,
-		 struct kvm_debug_exit_arch *arch_info);
-#endif
-	/*!
-	 * \brief Called when the VCPU issues an 'hlt' instruction.
-	 *
-	 * Typically, you should yeild here to prevent 100% CPU utilization
-	 * on the host CPU.
-	 */
-    int (*halt)(void *opaque, kvm_vcpu_context_t vcpu);
-    int (*shutdown)(void *opaque, void *env);
-    int (*io_window)(void *opaque);
-    int (*try_push_interrupts)(void *opaque);
-#ifdef KVM_CAP_USER_NMI
-    void (*push_nmi)(void *opaque);
-#endif
-    void (*post_kvm_run)(void *opaque, void *env);
-    int (*pre_kvm_run)(void *opaque, void *env);
-    int (*tpr_access)(void *opaque, kvm_vcpu_context_t vcpu, uint64_t rip, int is_write);
-#if defined(__s390__)
-    int (*s390_handle_intercept)(kvm_context_t context, kvm_vcpu_context_t vcpu,
-	struct kvm_run *run);
-    int (*s390_handle_reset)(kvm_context_t context, kvm_vcpu_context_t vcpu,
-	 struct kvm_run *run);
-#endif
-    int (*unhandled)(kvm_context_t context, kvm_vcpu_context_t vcpu,
-                     uint64_t hw_reason);
-};
-
-/*!
  * \brief Create new KVM context
  *
  * This creates a new kvm_context. A KVM context is a small area of data that
-- 
1.6.2.2


             reply	other threads:[~2009-07-08 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 12:34 Glauber Costa [this message]
2009-07-12  8:54 ` [PATCH] remove leftover: 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=1247056487-26739-1-git-send-email-glommer@redhat.com \
    --to=glommer@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@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;
as well as URLs for NNTP newsgroup(s).