All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>, kvm@vger.kernel.org
Cc: mst@redhat.com, afaerber@suse.de, agraf@suse.de
Subject: Re: [PATCH] kvm: x86: emulate monitor and mwait instructions as nop
Date: Wed, 07 May 2014 21:53:17 +0200	[thread overview]
Message-ID: <536A8F2D.4020305@redhat.com> (raw)
In-Reply-To: <20140507181056.GD1655@ERROL.INI.CMU.EDU>

Il 07/05/2014 20:10, Gabriel L. Somlo ha scritto:
>   1. I can't test svm.c (on AMD). As such, I'm not sure the
>      skip_emulated_instruction() call in my own version of nop_interception()
>      is necessary. If not, I could probably just call the already existing
>      nop_on_interception() (line 1926 or thereabouts in svm.c), which
>      just returns returns 1 without skipping anything.

Yes, it's necessary.

>   2. I get "defined but not used" warnings on invalid_op_interception() (svm.c)
>      and handle_invalid_op() (vmx.c). Apparently monitor/mwait are currently
>      the only VM exit reasons which lead to an "invalid opcode" exception.
>      Should my patch just nuke those functions (so that if anyone needs them
>      in the future they'd have to re-add them), or comment them out, or
>      call them after the "return 1;" statement in the monitor/mwait functions
>      to shut up gcc, or ??? :)

Nuke it. :)

Thanks for working on OS X virtualization, weird guests are always the 
source of interesting quirks!

Paolo

      parent reply	other threads:[~2014-05-07 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 18:10 [PATCH] kvm: x86: emulate monitor and mwait instructions as nop Gabriel L. Somlo
2014-05-07 18:15 ` Michael S. Tsirkin
2014-05-07 18:31   ` Alexander Graf
2014-05-07 19:53 ` Paolo Bonzini [this message]

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=536A8F2D.4020305@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=gsomlo@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.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.