qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "李 ヨンジュン" <getfeus@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Inject Interrupt, Using VMCS during qemu live migration.
Date: Sun, 9 Sep 2012 10:45:45 +0300	[thread overview]
Message-ID: <20120909074544.GA4109@redhat.com> (raw)
In-Reply-To: <504C084C.4080900@gmail.com>

On Sun, Sep 09, 2012 at 12:09:00PM +0900, 李 ヨンジュン wrote:
> Hello, I am trying to inject interrupt, in final phase of Live migration.
> 
> I use vmcs_write32 function to inject interrupt. This function is called
> by qemu, with ioctl.
> 
> This is Code.
> 
> (KVM)
> 
> void vmcs_write32_provider(unsigned long field, u32 value)
> {
> vmcs_write32(field, value);
> }
> 
> 
> long kvm_arch_vcpu_ioctl(struct file *filp,
> unsigned int ioctl, unsigned long arg)
> {
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~//
> case KVM_TEST_IOCTL: {
> r=0;
> //printk("Test IOCTL!!!\n");
> int type = 0;
> int trap=58;
> u32 intr_fields= (0x80000000 | (type<<8) | trap);
> vmcs_write32_provider(0x00004016,intr_fields);
> printk("vmcs_write Success!!!\n");
> 
> goto out;
> }
This is not how you inject interrupts in KVM. You are calling
kvm_set_irq() instead.

> 
> 
> This code works perfectly when called by hypercall.(When call this
> function in kvm_emulate_hypercall function by guest VM.)
> 
You mean this code sometimes accidentally has desirable effect.

> But, when I trying to call this function by qemu(ioctl), This error
> message is occurred.
> 
> http://pds23.egloos.com/pds/201209/09/86/f0062286_504c07a4bc3c7.png
> 
You are trying to inject interrupt when interrupts are disabled.

--
			Gleb.

  reply	other threads:[~2012-09-09  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09  3:09 [Qemu-devel] Inject Interrupt, Using VMCS during qemu live migration 李 ヨンジュン
2012-09-09  7:45 ` Gleb Natapov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-09  3:27 李 ヨンジュン

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=20120909074544.GA4109@redhat.com \
    --to=gleb@redhat.com \
    --cc=getfeus@gmail.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).