From: "H. Peter Anvin" <hpa@zytor.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner (tglx@linutronix.de)" <tglx@linutronix.de>,
"'mingo@elte.hu' (mingo@elte.hu)" <mingo@elte.hu>,
"Borislav Petkov (bp@alien8.de)" <bp@alien8.de>,
Satoru Moriya <satoru.moriya@hds.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"Luck, Tony (tony.luck@intel.com)" <tony.luck@intel.com>
Subject: Re: [PATCH v9 2/3] trace,x86: add x86 irq vector tracepoints
Date: Mon, 18 Feb 2013 20:39:19 -0800 [thread overview]
Message-ID: <512301F7.4020709@zytor.com> (raw)
In-Reply-To: <1361247854.23152.198.camel@gandalf.local.home>
On 02/18/2013 08:24 PM, Steven Rostedt wrote:
> On Mon, 2013-02-18 at 15:49 -0800, H. Peter Anvin wrote:
>
>> What about the following:
>>
>>> The base address of the IDT doesn't generally change... the one
>>> exception is when we do the funny NMI workaround.
>>>
>>> For that reason, I would be happier if we just restored the standard
>>> value instead of saving/restoring stuff.
>
> Basically what you are saying, is to have his code do what the NMI code
> originally did, but can't now, due to there being another IDT table
> (from Seiji's changes).
>
> static void switch_to_trace_idt(void *arg)
> {
> load_idt(&trace_idt_descr);
> }
>
> static void restore_original_idt(void *arg)
> {
> load_idt(this_cpu_ptr(&idt_descr));
> }
>
Yes. If there needs to be handshaking about whose IDT is currently
installed I'm much happier if that handshake is done explicitly, rather
than as a save/restore function which will break when we have to add
another one which for whatever reason isn't nesting.
-hpa
next prev parent reply other threads:[~2013-02-19 4:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 22:49 [PATCH v9 2/3] trace,x86: add x86 irq vector tracepoints Seiji Aguchi
2013-02-16 0:09 ` H. Peter Anvin
2013-02-16 1:59 ` Steven Rostedt
2013-02-16 2:11 ` H. Peter Anvin
2013-02-16 2:22 ` Steven Rostedt
2013-02-18 23:45 ` Seiji Aguchi
2013-02-18 23:49 ` H. Peter Anvin
2013-02-19 4:24 ` Steven Rostedt
2013-02-19 4:39 ` H. Peter Anvin [this message]
2013-02-19 4:41 ` Steven Rostedt
2013-02-19 21:00 ` Seiji Aguchi
2013-02-16 2:38 ` Steven Rostedt
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=512301F7.4020709@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=dle-develop@lists.sourceforge.net \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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