From: Shaohua Li <shli@fb.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<Kernel-team@fb.com>, Suresh Siddha <suresh.b.siddha@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] x86: serialize LVTT and TSC_DEADLINE write
Date: Sun, 2 Aug 2015 08:49:49 -0700 [thread overview]
Message-ID: <20150802154948.GA1432307@devbig257.prn2.facebook.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1508011202080.3825@nanos>
On Sat, Aug 01, 2015 at 12:10:41PM +0200, Thomas Gleixner wrote:
> On Fri, 31 Jul 2015, Shaohua Li wrote:
> > @@ -336,6 +336,22 @@ static void __setup_APIC_LVTT(unsigned int clocks, int oneshot, int irqen)
> > apic_write(APIC_LVTT, lvtt_value);
> >
> > if (lvtt_value & APIC_LVT_TIMER_TSCDEADLINE) {
> > + u64 msr;
> > +
> > + /*
> > + * See Intel SDM: TSC-Deadline Mode chapter. In xAPIC mode,
> > + * writing APIC LVTT and TSC_DEADLINE MSR isn't serialized.
> > + * This uses the algorithm described in Intel SDM to serialize
> > + * the two writes
> > + * */
> > + while (1) {
> > + wrmsrl(MSR_IA32_TSC_DEADLINE, -1L);
> > + rdmsrl(MSR_IA32_TSC_DEADLINE, msr);
> > + if (msr)
> > + break;
> > + }
> > + wrmsrl(MSR_IA32_TSC_DEADLINE, 0);
>
>
> I think this is exceptionally silly. A proper fence after the
> apic_write() should have the same effect.
Not sure what happens in the hardware, I could have a try of fence, but
I'd prefer using the algorithm Intel described. This is not a fast path,
the loop will exit immediately regardless the issue occurs anyway.
Thanks,
Shaohua
next prev parent reply other threads:[~2015-08-02 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 22:11 [PATCH] x86: serialize LVTT and TSC_DEADLINE write Shaohua Li
2015-08-01 10:10 ` Thomas Gleixner
2015-08-02 15:49 ` Shaohua Li [this message]
2015-08-02 19:41 ` Thomas Gleixner
2015-08-03 23:58 ` Shaohua Li
2015-08-05 8:44 ` Ingo Molnar
2015-08-05 16:25 ` Shaohua Li
2015-09-09 3:39 ` Andi Kleen
2015-09-09 4:13 ` Shaohua Li
2015-09-09 7:35 ` Thomas Gleixner
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=20150802154948.GA1432307@devbig257.prn2.facebook.com \
--to=shli@fb.com \
--cc=Kernel-team@fb.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).