From: Avi Kivity <avi@redhat.com>
To: Steven Rostedt <srostedt@redhat.com>
Cc: Luis Henriques <henrix@sapo.pt>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348
Date: Tue, 02 Dec 2008 22:38:55 +0200 [thread overview]
Message-ID: <49359CDF.5060300@redhat.com> (raw)
In-Reply-To: <1228249509.4886.11.camel@localhost.localdomain>
Steven Rostedt wrote:
> The following must be available without recursion for the function
> tracer to work:
>
> local_irq_save/restore
> smp_processor_id
> preempt_enable/disable_notrace
> atomic_inc/dec
>
In arch/x86/kvm/svm.c, function svm_vcpu_run(), everything between the
vmrun instruction and the call to load_host_msrs() is executed without a
live pda, so no smp_processor_id(). Could easily be fixed by
rearranging things.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-12-02 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 19:34 [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348 Luis Henriques
2008-11-30 20:20 ` Avi Kivity
2008-11-30 20:38 ` Luis Henriques
2008-11-30 20:44 ` Avi Kivity
2008-11-30 21:04 ` Luis Henriques
2008-12-02 12:23 ` Avi Kivity
2008-12-02 12:25 ` Avi Kivity
2008-12-02 12:31 ` Avi Kivity
2008-12-02 19:09 ` Luis Henriques
2008-12-02 19:27 ` Avi Kivity
2008-12-02 19:30 ` Avi Kivity
2008-12-02 19:46 ` Luis Henriques
2008-12-02 20:25 ` Steven Rostedt
2008-12-02 20:38 ` Avi Kivity [this message]
2008-12-02 20:48 ` Steven Rostedt
2008-12-02 20:56 ` Avi Kivity
2008-12-04 15:36 ` Avi Kivity
2008-12-04 22:05 ` Luis Henriques
2008-12-02 20:46 ` Luis Henriques
2008-12-02 21:16 ` Steven Rostedt
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=49359CDF.5060300@redhat.com \
--to=avi@redhat.com \
--cc=henrix@sapo.pt \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.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 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.