From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 115451] memset hang on pci device memory using kvm
Date: Wed, 06 Apr 2016 04:48:58 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.29.136]:44111 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1753862AbcDFEtD (ORCPT );
Wed, 6 Apr 2016 00:49:03 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 093C72034F
for ; Wed, 6 Apr 2016 04:49:01 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id E31A7202FE
for ; Wed, 6 Apr 2016 04:48:58 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=115451
--- Comment #2 from Gaurav Sharma ---
Following is the system info :
Host machine kernel version : 2.6.18-308.el5
Guest OS : Debian 3.2.0-4-686-pae
KVM vesrion : QEMU PC emulator version 0.9.1
Following are the steps to re-create the issue :
1. Boot the guest OS using QEMU with KVM enabled.
2. lspci will list down the pci devices configured on the guest OS.
3. I have a some PCI device configured with bar0 memory.
4. modify the pcimem.c application to use call memset
// This code is being modified to call memset to do a bulk write transaction
case 'w':
fprintf(stderr, "Before doing memset\n");
memset((virt_addr), 1, datalen);
fprintf(stderr, "after doing memset\n");
break;
5. Call the pcimem application to write on bar0 memory.
6. It results in memset call in hang, and the application needs to be
explicitly killed. I do not get the log message after memset call.
--
You are receiving this mail because:
You are watching the assignee of the bug.