From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLF7b-0006a5-7S for qemu-devel@nongnu.org; Thu, 17 Dec 2009 07:06:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLF7W-0006Um-52 for qemu-devel@nongnu.org; Thu, 17 Dec 2009 07:06:18 -0500 Received: from [199.232.76.173] (port=34401 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLF7V-0006UW-Rr for qemu-devel@nongnu.org; Thu, 17 Dec 2009 07:06:13 -0500 Received: from cantor.suse.de ([195.135.220.2]:41306 helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NLF7T-0004yr-R7 for qemu-devel@nongnu.org; Thu, 17 Dec 2009 07:06:12 -0500 From: Alexander Graf Date: Thu, 17 Dec 2009 13:06:09 +0100 Message-Id: <1261051569-7503-4-git-send-email-agraf@suse.de> In-Reply-To: <1261051569-7503-1-git-send-email-agraf@suse.de> References: <1261051569-7503-1-git-send-email-agraf@suse.de> Subject: [Qemu-devel] [PATCH 3/3] S390: Don't tell guest we're updating config space List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: aurelien@aurel32.net Currently we always set the "config space changed" bit to 1 when triggering any virtio interrupt. While that worked in 2.6.27, newer kernels interpret that value as "only the config space changed and nothing else happened". Since we usually trigger interrupts to tell the guest that something did happen, we just not tell it the config space changed for now until we implement the correct callback for that. Signed-off-by: Alexander Graf --- hw/s390-virtio-bus.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/hw/s390-virtio-bus.c b/hw/s390-virtio-bus.c index 493e4da..dc154ed 100644 --- a/hw/s390-virtio-bus.c +++ b/hw/s390-virtio-bus.c @@ -307,7 +307,7 @@ static void virtio_s390_notify(void *opaque, uint16_t vector) uint64_t token = s390_virtio_device_vq_token(dev, vector); /* XXX kvm dependency! */ - kvm_s390_virtio_irq(s390_cpu_addr2state(0), 1, token); + kvm_s390_virtio_irq(s390_cpu_addr2state(0), 0, token); } /**************** S390 Virtio Bus Device Descriptions *******************/ -- 1.6.0.2