All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "kvm" <kvm@vger.kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>,
	"Xiao Guangrong" <xiaoguangrong@linux.vnet.ibm.com>,
	"Michael S.Tsirkin" <mst@redhat.com>,
	"Gleb Natapov" <gleb@cloudius-systems.com>
Subject: [question] lots of interrupts injected to vm when pressing some key w/o releasing
Date: Thu, 20 Nov 2014 10:20:58 +0800	[thread overview]
Message-ID: <201411201020560455720@sangfor.com> (raw)

Hi all,

If I press the one of "Insert/Delete/Home/End/PageUp/PageDown/UpArrow/
DownArrow/LeftArrow/RightArrow" key w/o releasing, then lots of interrupts
will be injected to vm(win7/win2008), about 8000/s, the system become very slow,
bringing very bad experience. But the other keys are okay.
And, linux guest has no this problem.

If I remove the commit of 0bc830b05c667218d703f2026ec866c49df974fc, then the
problem disappeared, but win7 guest got stuck at booting stage.
And so strange that If the vm has only one vcpu, then the problem also disappeared.

Any ideas?

Thanks,
Zhang Haoyu


             reply	other threads:[~2014-11-20  2:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  2:20 Zhang Haoyu [this message]
2014-11-20  6:19 ` [question] lots of interrupts injected to vm when pressing some key w/o releasing Paolo Bonzini
2014-11-20  6:59   ` [question] lots of interrupts injected to vm when pressing somekey " Zhang Haoyu
2014-11-20  7:06     ` Gleb Natapov
2014-11-24  8:58       ` [question] lots of interrupts injected to vm when pressingsomekey " Zhang Haoyu
     [not found] ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABEF25B@SHSMSX104.ccr.corp.intel.com>
2014-11-21 22:31   ` [question] lots of interrupts injected to vm when pressing some key " Paolo Bonzini
     [not found]     ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF0FE3@SHSMSX104.ccr.corp.intel.com>
2014-11-25  9:49       ` Paolo Bonzini
     [not found]         ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF396A@SHSMSX104.ccr.corp.intel.com>
2014-12-03 15:42           ` Paolo Bonzini
2014-12-15  9:39             ` Zhang Haoyu
2014-12-15  9:40               ` Paolo Bonzini
2014-11-24 12:17 ` Zhang Haoyu
2014-11-24 12:25   ` Paolo Bonzini
2014-11-25  1:54     ` [question] lots of interrupts injected to vm when pressing somekey " Zhang Haoyu
2014-11-25  7:02       ` Paolo Bonzini
2014-11-25 11:20         ` Zhang Haoyu
2014-11-25 13:52           ` Paolo Bonzini
     [not found]             ` <201411261511537876936@sangfor.com>
     [not found]               ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF2A95@SHSMSX104.ccr.corp.intel.com>
2014-11-27  7:20                 ` [question] lots of interrupts injected to vm when pressing some key " Zhang Haoyu
     [not found]                   ` <A9667DDFB95DB7438FA9D7D576C3D87E0ABF2C24@SHSMSX104.ccr.corp.intel.com>
2014-11-27  8:54                     ` Zhang Haoyu
2014-11-28  8:27                   ` Wanpeng Li
2014-11-28  9:44                     ` Zhang Haoyu

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=201411201020560455720@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=alex.williamson@redhat.com \
    --cc=gleb@cloudius-systems.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    --cc=yang.z.zhang@intel.com \
    /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.