public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>,
	nikola.ciprich@linuxbox.cz, krucina@linuxbox.cz
Subject: Re: applications running in KVM crashing?
Date: Wed, 14 Jul 2010 17:00:39 +0300	[thread overview]
Message-ID: <4C3DC307.9050903@redhat.com> (raw)
In-Reply-To: <20100714134132.GC10153@develbox.linuxbox.cz>

On 07/14/2010 04:41 PM, Nikola Ciprich wrote:
>> disassembly around the failure please.
>>      
> hmm, is this what You want?
>
> (gdb) disas 0x00007f6391472273
> 0x00007f6391472273<pthread_rwlock_rdlock+99>:  lock decl (%rdi)
>    

By coincidence, a patch was sent yesterday fixing lock decl.  Can you 
try it out?

commit cb7eaecb3389c7fa2490ea1bee8f10cfa5df30d4
Author: Gleb Natapov <gleb@redhat.com>
Date:   Tue Jul 13 16:40:23 2010 +0300

     KVM: x86: emulator: inc/dec can have lock prefix

     Mark inc (0xfe/0 0xff/0) and dec (0xfe/1 0xff/1) as lock prefix 
capable.

     Signed-off-by: Gleb Natapov <gleb@redhat.com>
     Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

Although userspace code shouldn't invoke the emulator in most situations.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2010-07-14 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  4:14 applications running in KVM crashing? Nikola Ciprich
2010-06-09 12:00 ` Avi Kivity
2010-06-09 12:18   ` Nikola Ciprich
2010-07-14  9:45     ` Nikola Ciprich
2010-07-14 12:51       ` Avi Kivity
2010-07-14 13:41         ` Nikola Ciprich
2010-07-14 14:00           ` Avi Kivity [this message]
2010-07-14 14:32             ` Nikola Ciprich
2010-07-14 14:01           ` Gleb Natapov
2010-07-14 14:16             ` Nikola Ciprich
2010-07-14 14:26               ` Gleb Natapov

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=4C3DC307.9050903@redhat.com \
    --to=avi@redhat.com \
    --cc=extmaillist@linuxbox.cz \
    --cc=krucina@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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