From: Ingo Molnar <mingo@elte.hu>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH -rt] CONFIG_PARAVIRT and CONFIG_MCOUNT don't play well together
Date: Fri, 22 Jun 2007 10:33:30 +0200 [thread overview]
Message-ID: <20070622083330.GB19382@elte.hu> (raw)
In-Reply-To: <20070622080634.GP3723@sequoia.sous-sol.org>
* Chris Wright <chrisw@sous-sol.org> wrote:
> Current -rt is broken when compiling with CONFIG_PARAVIRT and
> CONFIG_MCOUNT both enabled. Because CONFIG_MCOUNT disables
> CONFIG_REGPARM, the calling convention must once again be explicit
> with fastcall. However, this was only half-way addressed in the -rt
> patch (adding fastcall back to paravirt_ops function ptr declaration
> but not the actual function definitions) so the compiled kernel has
> caller putting stuff in registers and callee pulling things from the
> stack. Impressive how far into boot it can get despite that ;-) Thanks
> to Steven Rostedt for prodding me and starting the initial debugging.
thanks! I ran into this before and asked for the fastcalls to not be
removed from upstream paravirt.c but to no avail it seems. It does no
harm to anyone to keep the 'fastcall' declarations and definitions for
places where _actual assembly code_ depends on the calling convention.
Could someone please send this upstream-wards too?
Ingo
next prev parent reply other threads:[~2007-06-22 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:06 Chris Wright
2007-06-22 8:33 ` Ingo Molnar [this message]
2007-06-22 15:29 ` Chris Wright
2007-06-22 15:32 ` Ingo Molnar
2007-06-22 16:19 ` Jeremy Fitzhardinge
2007-06-22 12:43 ` Steven Rostedt
2007-06-22 15:30 ` Chris Wright
2007-06-22 15:39 ` Ingo Molnar
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=20070622083330.GB19382@elte.hu \
--to=mingo@elte.hu \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®