From: Markus Metzger <markus.t.metzger@googlemail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"roland@redhat.com" <roland@redhat.com>,
"eranian@googlemail.com" <eranian@googlemail.com>,
"oleg@redhat.com" <oleg@redhat.com>,
"Villacis, Juan" <juan.villacis@intel.com>,
"ak@linux.jf.intel.com" <ak@linux.jf.intel.com>
Subject: Re: [patch] x86, bts: use atomic memory allocation
Date: Fri, 20 Mar 2009 19:59:51 +0100 [thread overview]
Message-ID: <1237575591.6387.2.camel@raistlin> (raw)
In-Reply-To: <20090320185559.GA6224@elte.hu>
On Fri, 2009-03-20 at 19:55 +0100, Ingo Molnar wrote:
> * Metzger, Markus T <markus.t.metzger@intel.com> wrote:
>
> > The second config boots OK with the additional changes to keep the
> > GFP_KERNEL and move the ds_request_bts() calls out of the
> > on_each_cpu() in the hw-branch-tracer.
> >
> > I don't know yet what exactly causes the crash and if there is a
> > simpler fix.
>
> hm, this was an AMD box - so perhaps they dont have a compatible DS
> implementation?
Hmmm, could be.
In that case, ds_cfg should be zero-initialized and ds_request should
return -EOPNOTSUPP. I'll try to simulate that.
regards,
markus.
next prev parent reply other threads:[~2009-03-20 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 18:27 [patch] x86, bts: use atomic memory allocation Markus Metzger
2009-03-19 16:11 ` Ingo Molnar
2009-03-20 8:07 ` Metzger, Markus T
2009-03-20 8:37 ` Andi Kleen
2009-03-20 16:23 ` Metzger, Markus T
2009-03-20 18:55 ` Ingo Molnar
2009-03-20 18:59 ` Markus Metzger [this message]
2009-03-25 9:07 ` Metzger, Markus T
2009-05-07 9:21 ` [tip:tracing/core] " tip-bot for Markus Metzger
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=1237575591.6387.2.camel@raistlin \
--to=markus.t.metzger@googlemail.com \
--cc=ak@linux.jf.intel.com \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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