public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] KVM: fix rcu usage in init_rmode_* functions
Date: Thu, 10 Mar 2011 12:22:38 +0200	[thread overview]
Message-ID: <4D78A66E.50209@redhat.com> (raw)
In-Reply-To: <4D772F10.3020302@cn.fujitsu.com>

On 03/09/2011 09:41 AM, Xiao Guangrong wrote:
> fix:
> [ 3494.671786] stack backtrace:
> [ 3494.671789] Pid: 10527, comm: qemu-system-x86 Not tainted 2.6.38-rc6+ #23
> [ 3494.671790] Call Trace:
> [ 3494.671796]  [] ? lockdep_rcu_dereference+0x9d/0xa5
> [ 3494.671826]  [] ? kvm_memslots+0x6b/0x73 [kvm]
> [ 3494.671834]  [] ? gfn_to_memslot+0x16/0x4f [kvm]
> [ 3494.671843]  [] ? gfn_to_hva+0x16/0x27 [kvm]
> [ 3494.671851]  [] ? kvm_write_guest_page+0x31/0x83 [kvm]
> [ 3494.671861]  [] ? kvm_clear_guest_page+0x1a/0x1c [kvm]
> [ 3494.671867]  [] ? vmx_set_tss_addr+0x83/0x122 [kvm_intel]
>
> and:
> [ 8328.789599] stack backtrace:
> [ 8328.789601] Pid: 18736, comm: qemu-system-x86 Not tainted 2.6.38-rc6+ #23
> [ 8328.789603] Call Trace:
> [ 8328.789609]  [] ? lockdep_rcu_dereference+0x9d/0xa5
> [ 8328.789621]  [] ? kvm_memslots+0x6b/0x73 [kvm]
> [ 8328.789628]  [] ? gfn_to_memslot+0x16/0x4f [kvm]
> [ 8328.789635]  [] ? gfn_to_hva+0x16/0x27 [kvm]
> [ 8328.789643]  [] ? kvm_write_guest_page+0x31/0x83 [kvm]
> [ 8328.789699]  [] ? kvm_clear_guest_page+0x1a/0x1c [kvm]
> [ 8328.789713]  [] ? vmx_create_vcpu+0x316/0x3c8 [kvm_intel]
>

Applied all four patches, thanks.

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


      parent reply	other threads:[~2011-03-10 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09  7:41 [PATCH v2 1/4] KVM: fix rcu usage in init_rmode_* functions Xiao Guangrong
2011-03-09  7:41 ` [PATCH v2 2/4] KVM: cleanup memslot_id function Xiao Guangrong
2011-03-09  7:43 ` [PATCH v2 3/4] KVM: MMU: introduce a common function to get no-dirty-logged slot Xiao Guangrong
2011-03-09  7:43 ` [PATCH v2 4/4] KVM: MMU: cleanup pte write path Xiao Guangrong
2011-03-10 10:21   ` Avi Kivity
2011-03-11  3:41     ` Xiao Guangrong
2011-03-10 10:22 ` Avi Kivity [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=4D78A66E.50209@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=xiaoguangrong@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox