From: Thomas Gleixner <tglx@linutronix.de>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Tony Luck <tony.luck@intel.com>, Alan Cox <alan@linux.intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [RFC PATCH 02/16] x86/split_lock: Handle #AC exception for split lock in kernel mode
Date: Sat, 23 Jun 2018 11:08:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1806231106080.8650@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180622231813.GE18979@romley-ivt3.sc.intel.com>
On Fri, 22 Jun 2018, Fenghua Yu wrote:
> On Fri, Jun 22, 2018 at 01:59:44PM +0200, Thomas Gleixner wrote:
> > On Fri, 22 Jun 2018, Thomas Gleixner wrote:
> > > The whole thing is simply:
> > >
> > > handle_ac()
> > > {
> > > if (user_mode(regs)) {
> > > do_trap(AC, SIGBUS, ...);
> > > } else {
> > > disable_ac_on_local_cpu();
> > > WARN_ONCE(1);
> > > }
> > > }
> > >
> > > That wants #AC enabled as early as possible so the kernel gets as much
> > > coverage as it can. If it trips in the kernel it's a bug and needs to be
> > > fixed and we can them fix ONE by ONE.
> >
> > That said, #AC is just yet another badly defined and hastily bolted on
> > (mis)feature. This should have been:
> >
> > Bit A: Enable #AC if CPL < 3
> > Bit B: Enable #AC if CPL == 3
> >
> > But that would have been too useful and would allow sensible use of #AC
> > without creating software trainwrecks.
> >
>
> The two bits would be ideal.
Correct. And if hardware people would not base their stuff on 'we expect'
assumptions and talk to us _before_ casting half baken features into
silicon, we would have two bits today.
Thanks,
tglx
next prev parent reply other threads:[~2018-06-23 9:09 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 15:45 [RFC PATCH 00/16] x86/split_lock: Enable #AC exception for split locked accesses Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 01/16] x86/split_lock: Add CONFIG and enumerate #AC exception for split locked access feature Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 02/16] x86/split_lock: Handle #AC exception for split lock in kernel mode Fenghua Yu
2018-06-21 19:46 ` Peter Zijlstra
2018-06-22 10:49 ` Thomas Gleixner
2018-06-22 11:59 ` Thomas Gleixner
2018-06-22 22:41 ` Fenghua Yu
2018-06-22 22:57 ` Thomas Gleixner
2018-06-22 23:03 ` Thomas Gleixner
2018-06-22 23:18 ` Fenghua Yu
2018-06-23 9:08 ` Thomas Gleixner [this message]
2018-06-23 4:20 ` Fenghua Yu
2018-06-23 9:17 ` Thomas Gleixner
2018-06-23 15:05 ` Fenghua Yu
2018-06-24 0:55 ` Thomas Gleixner
2018-06-24 1:17 ` Fenghua Yu
2018-06-24 6:43 ` Thomas Gleixner
2018-05-27 15:45 ` [RFC PATCH 03/16] x86/split_lock: Set up #AC exception for split locked accesses on all CPUs Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 04/16] x86/split_lock: Use non locked bit set instruction in set_cpu_cap Fenghua Yu
2018-06-21 19:55 ` Peter Zijlstra
2018-06-21 20:37 ` Thomas Gleixner
2018-06-27 23:35 ` Fenghua Yu
2018-06-28 7:53 ` Thomas Gleixner
2018-06-28 14:23 ` Fenghua Yu
2018-06-28 14:54 ` Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 05/16] x86/split_lock: Use non atomic set and clear bit instructions in clear_cpufeature() Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 06/16] x86/split_lock: Save #AC setting for split lock in firmware in boot time and restore the setting in reboot Fenghua Yu
2018-06-21 19:58 ` Peter Zijlstra
2018-06-22 15:11 ` Alan Cox
2018-06-26 9:05 ` Peter Zijlstra
2018-06-26 9:40 ` Thomas Gleixner
2018-06-26 11:02 ` Alan Cox
2018-06-26 11:31 ` Peter Zijlstra
2018-05-27 15:45 ` [RFC PATCH 07/16] x86/split_lock: Handle suspend/hibernate and resume Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 08/16] x86/split_lock: Set split lock during EFI runtime service Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 09/16] x86/split_lock: Add CONFIG to control #AC for split lock at boot time Fenghua Yu
2018-05-27 15:45 ` [RFC PATCH 10/16] x86/split_lock: Add a debugfs interface to allow user to enable or disable #AC for split lock during run time Fenghua Yu
2018-05-29 18:43 ` Greg KH
2018-05-27 15:46 ` [RFC PATCH 11/16] x86/split_lock: Add CONFIG to control #AC for split lock from kernel at boot time Fenghua Yu
2018-05-27 15:46 ` [RFC PATCH 12/16] x86/split_lock: Add a debugfs interface to allow user to change how to handle split lock in kernel mode during run time Fenghua Yu
2018-05-27 15:46 ` [RFC PATCH 13/16] x86/split_lock: Add debugfs interface to control user mode behavior Fenghua Yu
2018-05-27 15:46 ` [RFC PATCH 14/16] x86/split_lock: Add debugfs interface to show and control firmware setting for split lock Fenghua Yu
2018-05-27 15:46 ` [RFC PATCH 15/16] x86/split_lock: Add CONFIG and debugfs interface for testing #AC for split lock in kernel mode Fenghua Yu
2018-05-27 15:46 ` [RFC PATCH 16/16] x86/split_lock: Add user space split lock test in selftest Fenghua Yu
2018-05-29 16:39 ` [RFC PATCH 00/16] x86/split_lock: Enable #AC exception for split locked accesses Dave Hansen
2018-05-29 17:25 ` Fenghua Yu
2018-05-29 17:28 ` Dave Hansen
2018-05-29 17:40 ` Fenghua Yu
2018-05-29 16:40 ` Dave Hansen
2018-05-29 17:38 ` Fenghua Yu
2018-06-21 20:06 ` Peter Zijlstra
2018-06-21 19:37 ` Peter Zijlstra
2018-06-21 20:18 ` Fenghua Yu
2018-06-21 20:32 ` Thomas Gleixner
2018-06-21 22:00 ` Fenghua Yu
2018-06-21 22:07 ` Peter Zijlstra
2018-06-21 22:08 ` Peter Zijlstra
2018-06-21 22:18 ` Dave Hansen
2018-06-21 22:42 ` Fenghua Yu
2018-06-22 8:11 ` Peter Zijlstra
2018-06-22 9:30 ` Thomas Gleixner
2018-06-21 22:10 ` Peter Zijlstra
2018-06-21 23:05 ` Fenghua Yu
2018-06-22 8:19 ` Peter Zijlstra
2018-06-21 22:11 ` Peter Zijlstra
2018-06-21 22:43 ` Fenghua Yu
2018-06-21 22:13 ` Peter Zijlstra
2018-06-23 18:47 ` Fenghua Yu
2018-06-22 9:18 ` Thomas Gleixner
2018-06-22 9:22 ` Thomas Gleixner
2018-06-22 9:25 ` Thomas Gleixner
2018-06-22 9:28 ` Thomas Gleixner
2018-06-21 20:36 ` Peter Zijlstra
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=alpine.DEB.2.21.1806231106080.8650@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alan@linux.intel.com \
--cc=arjan@infradead.org \
--cc=ashok.raj@intel.com \
--cc=dave.hansen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rafael.j.wysocki@intel.com \
--cc=ravi.v.shankar@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).