All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 115451] memset hang on pci device memory using kvm
Date: Wed, 06 Apr 2016 04:48:58 +0000	[thread overview]
Message-ID: <bug-115451-28872-EgrpiRUYbT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-115451-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=115451

--- Comment #2 from Gaurav Sharma <gauravs.2010@gmail.com> ---
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.

  parent reply	other threads:[~2016-04-06  4:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  9:59 [Bug 115451] New: memset hang on pci device memory using kvm bugzilla-daemon
2016-03-29 16:34 ` [Bug 115451] " bugzilla-daemon
2016-04-06  4:48 ` bugzilla-daemon [this message]
2016-04-06  5:27 ` bugzilla-daemon
2016-04-06  8:27 ` bugzilla-daemon
2016-04-06  8:32 ` bugzilla-daemon
2016-04-06  9:30 ` bugzilla-daemon
2016-04-06  9:40 ` bugzilla-daemon
2016-04-06  9:41 ` bugzilla-daemon

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=bug-115451-28872-EgrpiRUYbT@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.