Thread (39 messages) 39 messages, 3 authors, 2012-10-30

Re: [PATCH 04/12] VMCI: device driver implementaton.

From: Greg KH <gregkh@linuxfoundation.org>
Date: 2012-10-30 02:20:50
Also in: lkml

On Mon, Oct 29, 2012 at 06:04:15PM -0700, George Zhang wrote:
+/*
+ * vmci_get_context_id() - Gets the current context ID.
+ *
+ * Returns the current context ID.  Note that since this is accessed only
+ * from code running in the host, this always returns the host context ID.
+ */
+u32 vmci_get_context_id(void)
+{
+	if (vmci_guest_code_active()) {
+		return vmci_get_vm_context_id();
+	} else if (vmci_host_code_active()) {
+		return VMCI_HOST_CONTEXT_ID;
+	} else {
+		return VMCI_INVALID_ID;
+	}
+}
+EXPORT_SYMBOL_GPL(vmci_get_context_id);
checkpatch didn't complain about too many { } here?
+/*
+ * vmci_version() - Returns the version of the driver.
+ *
+ * Returns the version of the VMCI driver.
+ */
+u32 vmci_version(void)
+{
+	return VMCI_VERSION;
+}
+EXPORT_SYMBOL_GPL(vmci_version);
Why is this needed?  Why would a kernel driver ever care about this?

thanks,

greg k-h
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help