From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] KVM: Emulate multibyte NOP
Date: Mon, 3 Jun 2013 11:21:08 +0300 [thread overview]
Message-ID: <20130603082108.GB4725@redhat.com> (raw)
In-Reply-To: <1369912959-18715-1-git-send-email-pbonzini@redhat.com>
On Thu, May 30, 2013 at 01:22:39PM +0200, Paolo Bonzini wrote:
> This is encountered when booting RHEL5.9 64-bit. There is another bug
> after this one that is not a simple emulation failure, but this one lets
> the boot proceed a bit.
>
> Cc: <stable@vger.kernel.org> # 3.9
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Applied to master, thanks.
> ---
> arch/x86/kvm/emulate.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index 48e6abd..aa68106 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -3987,7 +3987,8 @@ static const struct opcode twobyte_table[256] = {
> DI(ImplicitOps | Priv, invd), DI(ImplicitOps | Priv, wbinvd), N, N,
> N, D(ImplicitOps | ModRM), N, N,
> /* 0x10 - 0x1F */
> - N, N, N, N, N, N, N, N, D(ImplicitOps | ModRM), N, N, N, N, N, N, N,
> + N, N, N, N, N, N, N, N,
> + D(ImplicitOps | ModRM), N, N, N, N, N, N, D(ImplicitOps | ModRM),
> /* 0x20 - 0x2F */
> DIP(ModRM | DstMem | Priv | Op3264, cr_read, check_cr_read),
> DIP(ModRM | DstMem | Priv | Op3264, dr_read, check_dr_read),
> @@ -4822,6 +4823,7 @@ twobyte_insn:
> case 0x08: /* invd */
> case 0x0d: /* GrpP (prefetch) */
> case 0x18: /* Grp16 (prefetch/nop) */
> + case 0x1f: /* nop */
> break;
> case 0x20: /* mov cr, reg */
> ctxt->dst.val = ops->get_cr(ctxt, ctxt->modrm_reg);
> --
> 1.8.1.4
--
Gleb.
prev parent reply other threads:[~2013-06-03 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 11:22 [PATCH] KVM: Emulate multibyte NOP Paolo Bonzini
2013-06-03 8:21 ` Gleb Natapov [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=20130603082108.GB4725@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).