From: Andy Lutomirski <luto@amacapital.net>
To: Borislav Petkov <bp@suse.de>
Cc: x86-ml <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86: Kill notsc
Date: Sun, 18 Oct 2015 21:47:21 -0700 [thread overview]
Message-ID: <CALCETrX=MZKdOT+QHYPJcKe_ue-s0pjKZiYLejMPJWnXLkhv9A@mail.gmail.com> (raw)
In-Reply-To: <20151018142007.GA11294@pd.tnic>
On Sun, Oct 18, 2015 at 7:20 AM, Borislav Petkov <bp@suse.de> wrote:
> Ok,
>
> let's try this and see where it takes us. Patch has been only lightly
> tested in kvm - I'll hammer on it for real once we agree about the
> general form.
>
> Aanyway, this patch is something Peter and I have been talking about on
> IRC a couple of times already. I finally found some free time to poke at
> it, here's the result.
>
> Thoughts?
I'm a bit confused. Is it currently the case that, if you boot a
normal kernel on a TSC-less machine without notsc, it fails?
--Andy
next prev parent reply other threads:[~2015-10-19 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 14:20 [RFC PATCH] x86: Kill notsc Borislav Petkov
2015-10-19 4:47 ` Andy Lutomirski [this message]
2015-10-19 8:16 ` Borislav Petkov
2015-10-21 17:58 ` Borislav Petkov
2015-10-21 19:01 ` Peter Zijlstra
2015-10-22 18:51 ` [PATCH -v2] " Borislav Petkov
2015-11-04 10:21 ` Thomas Gleixner
2015-11-04 10:29 ` Borislav Petkov
2015-11-16 18:45 ` [RFC PATCH -v2.1] " Borislav Petkov
2015-11-16 21:25 ` Thomas Gleixner
2015-11-17 5:02 ` H. Peter Anvin
2015-11-17 8:53 ` Borislav Petkov
2015-11-17 9:11 ` Thomas Gleixner
2015-11-17 9:33 ` Borislav Petkov
2015-11-17 10:08 ` Thomas Gleixner
2015-11-17 11:09 ` Borislav Petkov
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='CALCETrX=MZKdOT+QHYPJcKe_ue-s0pjKZiYLejMPJWnXLkhv9A@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.