Chris Wright wrote:
> * Steven Rostedt ([EMAIL PROTECTED]) wrote:
>
>> Hmm, I know paravirt-ops had an issue with mcount in the RT tree. I can't
>> remember the exact issues, but it did have something to do with the way
>> parameters were passed in.
>>
>> Chris, do you remember what the issues
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
> On Thu, 3 Jan 2008, Chris Wright wrote:
> > Yes, paravirt ops have a well-specified calling convention (register
> > based). There was a cleanup that Andi did that caused the problem
> > because it removed all the "fastcall" annotations since
On Thu, 3 Jan 2008, Chris Wright wrote:
>
> Yes, paravirt ops have a well-specified calling convention (register
> based). There was a cleanup that Andi did that caused the problem
> because it removed all the "fastcall" annotations since -mregparm=3
> is now always on for i386. Since MCOUNT
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
> Hmm, I know paravirt-ops had an issue with mcount in the RT tree. I can't
> remember the exact issues, but it did have something to do with the way
> parameters were passed in.
>
> Chris, do you remember what the issues were?
Yes, paravirt ops have a
On Thu, 3 Jan 2008, Mathieu Desnoyers wrote:
> .
> > Index: linux-compile.git/arch/x86/kernel/mcount-wrapper.S
> > ===
> > --- /dev/null 1970-01-01 00:00:00.0 +
> > +++
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
...
> Index: linux-compile.git/arch/x86/Kconfig
> ===
> --- linux-compile.git.orig/arch/x86/Kconfig 2008-01-03 01:02:28.0
> -0500
> +++ linux-compile.git/arch/x86/Kconfig
On Thu, 2008-01-03 at 02:16 -0500, Steven Rostedt wrote:
> Index: linux-compile.git/Makefile
> ===
> --- linux-compile.git.orig/Makefile 2008-01-03 01:02:28.0 -0500
> +++ linux-compile.git/Makefile 2008-01-03
Hi Sam!
On Thu, 3 Jan 2008, Sam Ravnborg wrote:
> > ---
> >
> > Index: linux-compile.git/Documentation/stable_api_nonsense.txt
> > ===
> > --- linux-compile.git.orig/Documentation/stable_api_nonsense.txt
> > 2008-01-03
[Added Chris Wright, Rusty and Virt list because they were involved with
this issue before]
On Thu, 3 Jan 2008, Ingo Molnar wrote:
>
> * Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> > +# function tracing might turn this off:
> > +config REGPARM
> > + bool
> > + depends on !MCOUNT
> > +
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> +# function tracing might turn this off:
> +config REGPARM
> + bool
> + depends on !MCOUNT
> + default y
are you sure -pg really needs this? I just carried this along the years
and went the path of least resistence, but we should not be
Hi Steven.
On Thu, Jan 03, 2008 at 02:16:10AM -0500, Steven Rostedt wrote:
> If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
> non-zero value the mcount routine will be called everytime we enter a kernel
> function that is not marked with the "notrace" attribute.
>
>
Hi Steven.
On Thu, Jan 03, 2008 at 02:16:10AM -0500, Steven Rostedt wrote:
If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
non-zero value the mcount routine will be called everytime we enter a kernel
function that is not marked with the notrace attribute.
The
* Steven Rostedt [EMAIL PROTECTED] wrote:
+# function tracing might turn this off:
+config REGPARM
+ bool
+ depends on !MCOUNT
+ default y
are you sure -pg really needs this? I just carried this along the years
and went the path of least resistence, but we should not be
[Added Chris Wright, Rusty and Virt list because they were involved with
this issue before]
On Thu, 3 Jan 2008, Ingo Molnar wrote:
* Steven Rostedt [EMAIL PROTECTED] wrote:
+# function tracing might turn this off:
+config REGPARM
+ bool
+ depends on !MCOUNT
+ default y
are
On Thu, 2008-01-03 at 02:16 -0500, Steven Rostedt wrote:
Index: linux-compile.git/Makefile
===
--- linux-compile.git.orig/Makefile 2008-01-03 01:02:28.0 -0500
+++ linux-compile.git/Makefile 2008-01-03
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
...
Index: linux-compile.git/arch/x86/Kconfig
===
--- linux-compile.git.orig/arch/x86/Kconfig 2008-01-03 01:02:28.0
-0500
+++ linux-compile.git/arch/x86/Kconfig
On Thu, 3 Jan 2008, Mathieu Desnoyers wrote:
.
Index: linux-compile.git/arch/x86/kernel/mcount-wrapper.S
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ linux-compile.git/arch/x86/kernel/mcount-wrapper.S
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
Hmm, I know paravirt-ops had an issue with mcount in the RT tree. I can't
remember the exact issues, but it did have something to do with the way
parameters were passed in.
Chris, do you remember what the issues were?
Yes, paravirt ops have a
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
On Thu, 3 Jan 2008, Chris Wright wrote:
Yes, paravirt ops have a well-specified calling convention (register
based). There was a cleanup that Andi did that caused the problem
because it removed all the fastcall annotations since -mregparm=3
is
On Thu, 3 Jan 2008, Chris Wright wrote:
Yes, paravirt ops have a well-specified calling convention (register
based). There was a cleanup that Andi did that caused the problem
because it removed all the fastcall annotations since -mregparm=3
is now always on for i386. Since MCOUNT disables
Chris Wright wrote:
* Steven Rostedt ([EMAIL PROTECTED]) wrote:
Hmm, I know paravirt-ops had an issue with mcount in the RT tree. I can't
remember the exact issues, but it did have something to do with the way
parameters were passed in.
Chris, do you remember what the issues were?
If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
non-zero value the mcount routine will be called everytime we enter a kernel
function that is not marked with the "notrace" attribute.
The mcount routine will then call a registered function if a function
happens to be
If CONFIG_MCOUNT is selected and /proc/sys/kernel/mcount_enabled is set to a
non-zero value the mcount routine will be called everytime we enter a kernel
function that is not marked with the notrace attribute.
The mcount routine will then call a registered function if a function
happens to be
23 matches
Mail list logo
