From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: x86: split spinlock implementations out into their own files
Date: Thu, 24 Jul 2008 12:32:23 +0200 [thread overview]
Message-ID: <20080724103223.GE28817@elte.hu> (raw)
In-Reply-To: <4887948A.9070301@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> ftrace requires certain low-level code, like spinlocks and timestamps,
> to be compiled without -pg in order to avoid infinite recursion. This
> patch splits out the core paravirt spinlocks and the Xen spinlocks
> into separate files which can be compiled without -pg.
>
> Also do xen/time.c while we're about it. As a result, we can now use
> ftrace within a Xen domain.
applied to x86/spinlocks, thanks Jeremy.
Ingo
prev parent reply other threads:[~2008-07-24 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 20:28 x86: split spinlock implementations out into their own files Jeremy Fitzhardinge
2008-07-24 10:32 ` Ingo Molnar [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=20080724103223.GE28817@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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