All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Failed vm entry with heavy use of emulator
Date: Tue, 5 Jan 2016 16:37:12 +0200	[thread overview]
Message-ID: <568BD518.8080000@bitdefender.com> (raw)
In-Reply-To: <CABfawhkFKMu_mcYF9b8=pQ_eSa9WWFraVQoive81oxkYTBigWg@mail.gmail.com>

On 01/05/2016 04:16 PM, Tamas K Lengyel wrote:
> 
> 
> On Tue, Jan 5, 2016 at 3:01 PM, Razvan Cojocaru
> <rcojocaru@bitdefender.com <mailto:rcojocaru@bitdefender.com>> wrote:
> 
>     On 01/05/2016 03:49 PM, Andrew Cooper wrote:
>     > On 05/01/16 13:39, Razvan Cojocaru wrote:
>     >> Here's a quick log of the emulated instructions on my setup:
>     >> http://pastebin.com/raw/XXQ0Lnzh
>     >
>     > Hmm - according to that, the final instruction emulated was
>     >
>     > d1v0 32bit @ 0008:828925db -> fa
>     >
>     > which is the 'cli' instruction.
>     >
>     > I would start there - I doubt it is an instruction which is emulated often.
> 
>     My code (arch/x86/x86_emulate/x86_emulate.c) does have a case label
>     for it:
> 
>     3677     case 0xfa: /* cli */
>     3678         generate_exception_if(!mode_iopl(), EXC_GP, 0);
>     3679         _regs.eflags &= ~EFLG_IF;
>     3680         break;
> 
>     Maybe the IOPL test fails there? Tamas, does your guest die after a CLI
>     as well?
> 
> 
> I've added a gdprintk(XENLOG_DEBUG, "emulate 0xfa cli\n"); into that
> switch case but it wasn't printed before the guest crashed.

It's possible that your guest crashes after emulating a different
instruction. I've added a line to xen/arch/x86/hvm/emulate.c, in
hvm_mem_access_emulate_one():

1790     switch ( kind )
1791     {
1792     case EMUL_KIND_NOWRITE:
1793         rc = hvm_emulate_one_no_write(&ctx);
1794         break;
1795     case EMUL_KIND_SET_CONTEXT:
1796         ctx.set_context = 1;
1797         /* Intentional fall-through. */
1798     default:
1799         rc = hvm_emulate_one(&ctx);
1800         hvm_dump_emulation_state(XENLOG_G_DEBUG, &ctx);
1801     }

so I can then see which instruction was the last before the stack trace
with xl dmesg (or looking at the log file, etc.)

It's possible the problem is not specific to CLI, or maybe it's even
something that happens prior to emulating the last instruction that
leads to a corruption in the guest's state later on.


Cheers,
Razvan

  reply	other threads:[~2016-01-05 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 11:49 Failed vm entry with heavy use of emulator Tamas K Lengyel
2016-01-05 11:56 ` Andrew Cooper
2016-01-05 12:05   ` Tamas K Lengyel
2016-01-05 13:45     ` Andrew Cooper
2016-01-06 14:21     ` Jan Beulich
2016-01-05 13:39   ` Razvan Cojocaru
2016-01-05 13:49     ` Andrew Cooper
2016-01-05 14:01       ` Razvan Cojocaru
2016-01-05 14:12         ` Andrew Cooper
2016-01-05 14:16         ` Tamas K Lengyel
2016-01-05 14:37           ` Razvan Cojocaru [this message]
2016-09-06 23:31             ` Tamas K Lengyel
2016-09-07  5:59               ` Razvan Cojocaru
2016-09-07  9:36                 ` Jan Beulich
2016-01-05 12:35 ` Razvan Cojocaru

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=568BD518.8080000@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=tamas.k.lengyel@gmail.com \
    --cc=xen-devel@lists.xen.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 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.