public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Joerg Rodel <joerg.roedel@amd.com>,
	kvm@vger.kernel.org, stable@kernel.org,
	Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH] KVM: SVM: fix random segfaults with NPT enabled
Date: Wed, 27 Aug 2008 18:50:27 +0300	[thread overview]
Message-ID: <48B577C3.3050302@qumranet.com> (raw)
In-Reply-To: <20080827153550.GB3801@8bytes.org>

Joerg Roedel wrote:
> On Wed, Aug 27, 2008 at 06:22:14PM +0300, Avi Kivity wrote:
>   
>> Joerg Rodel wrote:
>>     
>>> I will test it. Is the fix in your latest kernel.org tree? 
>>>       
>> It is now.  It doesn't fix the problem.
>>
>>     
>>> Reproduce it
>>> with a KVM guest and start tbench in it with around 100 clients
>>> configured. The tbench-process will crash when the bug is hit.
>>>  
>>>       
>> Does it reproduce with uniprocessor guests?
>>     
>
> Don't know yet. We will try that.
>
>   

It didn't reproduce here on uniprocessor, but I hadn't tried for long.

Some observations:

- tbench triggers many cases where we have concurrent faults on the same 
address.  these are serialized by mmu_lock.  I tried to have  
direct_map_entry() return is it detects a race.  didn't help.
- I instrumented set_shadow_pte() to warn if changing the pfn or 
writeable bit.  Didn't trip.

Are there any rules for touching npt ptes concurrently?

Meanwhile, I applied the patch, but I'm very worried about this.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-08-27 15:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 12:18 [PATCH] KVM: SVM: fix random segfaults with NPT enabled Joerg Rodel
2008-08-27 13:11 ` Avi Kivity
2008-08-27 13:53   ` Joerg Rodel
2008-08-27 15:21     ` Avi Kivity
2008-08-27 15:32       ` Joerg Roedel
2008-08-27 13:53   ` Avi Kivity
2008-08-27 13:57     ` Joerg Rodel
2008-08-27 15:22       ` Avi Kivity
2008-08-27 15:35         ` Joerg Roedel
2008-08-27 15:50           ` Avi Kivity [this message]
2008-08-27 16:27             ` Joerg Rodel
2008-08-27 16:49               ` Avi Kivity
2008-08-27 16:59                 ` Avi Kivity
2008-08-28 14:58                   ` Joerg Rodel
2008-08-28 15:15                     ` Avi Kivity
2008-08-28 15:19                       ` Joerg Roedel
2008-08-28 15:47                         ` Avi Kivity
2008-08-28 15:29                       ` Avi Kivity
2008-08-28 15:58                         ` Joerg Roedel

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=48B577C3.3050302@qumranet.com \
    --to=avi@qumranet.com \
    --cc=agraf@suse.de \
    --cc=joerg.roedel@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=stable@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