linux-kernel - [tip:tools/kvm] kvmtool: Adjust to new upstream virtio constants

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <tip-4f24511d36c9e41b42a53a6cf5d4b970e013fdfd@git.kernel.org>
Date:	Fri, 1 May 2015 07:17:22 -0700
From:	tip-bot for Ingo Molnar <tipbot@...or.com>
To:	linux-tip-commits@...r.kernel.org
Cc:	will.deacon@....com, linux-kernel@...r.kernel.org, hpa@...or.com,
	mingo@...nel.org, penberg@....fi, tglx@...utronix.de
Subject: [tip:tools/kvm] kvmtool: Adjust to new upstream virtio constants

Commit-ID:  4f24511d36c9e41b42a53a6cf5d4b970e013fdfd
Gitweb:     http://git.kernel.org/tip/4f24511d36c9e41b42a53a6cf5d4b970e013fdfd
Author:     Ingo Molnar <mingo@...nel.org>
AuthorDate: Mon, 16 Mar 2015 15:26:20 +0100
Committer:  Ingo Molnar <mingo@...nel.org>
CommitDate: Fri, 1 May 2015 16:11:58 +0200

kvmtool: Adjust to new upstream virtio constants

tools/kvm won't build on newer kernels, due to the rename in:

 1862ee22ce2e ("virtio-mmio: Update the device to OASIS spec version")

adjust the code to the new names.

Cc: Pekka Enberg <penberg@....fi>
Cc: Will Deacon <will.deacon@....com>
Link: http://lkml.kernel.org/r/20150316142620.GA30206@gmail.com
Signed-off-by: Ingo Molnar <mingo@...nel.org>
---
 tools/kvm/virtio/mmio.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/tools/kvm/virtio/mmio.c b/tools/kvm/virtio/mmio.c
index 5174455..1587d5c 100644
--- a/tools/kvm/virtio/mmio.c
+++ b/tools/kvm/virtio/mmio.c
@@ -122,7 +122,7 @@ static void virtio_mmio_config_in(struct kvm_cpu *vcpu,
 	case VIRTIO_MMIO_INTERRUPT_STATUS:
 		ioport__write32(data, *(u32 *)(((void *)&vmmio->hdr) + addr));
 		break;
-	case VIRTIO_MMIO_HOST_FEATURES:
+	case VIRTIO_MMIO_DEVICE_FEATURES:
 		if (vmmio->hdr.host_features_sel == 0)
 			val = vdev->ops->get_host_features(vmmio->kvm,
 							   vmmio->dev);
@@ -152,8 +152,8 @@ static void virtio_mmio_config_out(struct kvm_cpu *vcpu,
 	u32 val = 0;
 
 	switch (addr) {
-	case VIRTIO_MMIO_HOST_FEATURES_SEL:
-	case VIRTIO_MMIO_GUEST_FEATURES_SEL:
+	case VIRTIO_MMIO_DEVICE_FEATURES_SEL:
+	case VIRTIO_MMIO_DRIVER_FEATURES_SEL:
 	case VIRTIO_MMIO_QUEUE_SEL:
 		val = ioport__read32(data);
 		*(u32 *)(((void *)&vmmio->hdr) + addr) = val;
@@ -165,7 +165,7 @@ static void virtio_mmio_config_out(struct kvm_cpu *vcpu,
 		if (vdev->ops->notify_status)
 			vdev->ops->notify_status(kvm, vmmio->dev, vmmio->hdr.status);
 		break;
-	case VIRTIO_MMIO_GUEST_FEATURES:
+	case VIRTIO_MMIO_DRIVER_FEATURES:
 		if (vmmio->hdr.guest_features_sel == 0) {
 			val = ioport__read32(data);
 			vdev->ops->set_guest_features(vmmio->kvm,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/