From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Ingo Molnar <mingo@elte.hu>, 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 09:19:41 -0700 [thread overview]
Message-ID: <467BF69D.4030806@goop.org> (raw)
In-Reply-To: <20070622152915.GQ3723@sequoia.sous-sol.org>
Chris Wright wrote:
> Yes, I agree, it's actually documenting the subtlety of the calling
> convention, not just noise in the source. The upstream patch is
> different, I'll sort one out.
I wonder if we should use something like "regparm" rather than
"fastcall"? The latter makes it sound like its just a performance issue.
J
next prev parent reply other threads:[~2007-06-22 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:06 [PATCH -rt] CONFIG_PARAVIRT and CONFIG_MCOUNT don't play well together Chris Wright
2007-06-22 8:33 ` Ingo Molnar
2007-06-22 15:29 ` Chris Wright
2007-06-22 15:32 ` Ingo Molnar
2007-06-22 16:19 ` Jeremy Fitzhardinge [this message]
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=467BF69D.4030806@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).