From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: akataria@vmware.com, the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: VMI broken on tip/master...
Date: Sat, 14 Mar 2009 16:45:05 -0700 [thread overview]
Message-ID: <49BC4181.70603@goop.org> (raw)
In-Reply-To: <1237072800.8939.813.camel@laptop>
Peter Zijlstra wrote:
> So what was supposed to be a simple op, now gets expanded into god knows
> what, and might lead to tracer recursion or something.
I don't think that's relevent in this case; Alok's report is not that
this code crashes, but that this changeset causes a crash somewhere in
the VMI/paravirt patching code. Very odd.
J
next prev parent reply other threads:[~2009-03-14 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 17:56 VMI broken on tip/master Alok Kataria
2009-03-14 23:20 ` Peter Zijlstra
2009-03-14 23:45 ` Jeremy Fitzhardinge [this message]
2009-03-16 16:04 ` Steven Rostedt
2009-03-16 22:03 ` Jeremy Fitzhardinge
2009-03-14 23:45 ` Jeremy Fitzhardinge
2009-03-16 22:42 ` Alok Kataria
2009-03-16 22:54 ` Jeremy Fitzhardinge
2009-03-16 23:49 ` Alok Kataria
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=49BC4181.70603@goop.org \
--to=jeremy@goop.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akataria@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=x86@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