mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@qumranet.com>
To: kvm-devel@lists.sourceforge.net
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	linux-kernel@vger.kernel.org, Avi Kivity <avi@qumranet.com>
Subject: Re: [kvm-devel] [PATCH] Refactor hypercall infrastructure (v2)
Date: Mon, 3 Dec 2007 14:16:51 +0530	[thread overview]
Message-ID: <200712031416.51710.amit.shah@qumranet.com> (raw)
In-Reply-To: <475339A6.9020207@us.ibm.com>

* Anthony Liguori wrote:
> Amit Shah wrote:
> > * Anthony Liguori wrote:
> >  
> >
> >> This patch refactors the current hypercall infrastructure to better
> >> support live migration and SMP.  It eliminates the hypercall page by
> >> trapping the UD exception that would occur if you used the wrong
> >> hypercall instruction for the underlying architecture and replacing it
> >> with the right one lazily. 
> >
> > This doesn't work right for SVM. It keeps looping indefinitely; on a
> > kvm_stat run, I get about 230,000 light vm exits per second, with the
> > hypercall never returning to the guest.
> >
> > ...
> >  
>
> What are you using to issue the hypercall?

+       r = kvm_hypercall1(KVM_PV_PCI_DEVICE, page_gfn);

Setup is done by:

+       if (!kvm_para_available()) {
+               printk(KERN_ERR "KVM paravirt support not available\n");
+               r = -ENODEV;
+               goto out_dereg;
+       }

I also couldn't get the has_feature to work properly.

See:

http://lkml.org/lkml/2007/11/7/129

I had to change the hypercall address to 0f 01 d9 for it to get working.

>
> Regards,
>
> Anthony Liguori



  reply	other threads:[~2007-12-03  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 17:54 Anthony Liguori
2007-09-16  9:08 ` Avi Kivity
2007-12-02 13:47 ` [kvm-devel] " Amit Shah
2007-12-02 14:32   ` Avi Kivity
2007-12-02 23:03   ` Anthony Liguori
2007-12-03  8:46     ` Amit Shah [this message]
2007-12-03  9:00       ` Avi Kivity
2007-12-03 11:30         ` Amit Shah

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=200712031416.51710.amit.shah@qumranet.com \
    --to=amit.shah@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®