The pull request you sent on Sun, 11 Apr 2021 11:03:32 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.12-rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/06f838e02d3b6e161df08c910e12e8366f1cb465
Thank you!
--
Hi Linus,
please pull two more urgent fixes (not gonna say "final" this time) from
x86-land.
Thx.
---
The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
are available in the Git repository at:
The pull request you sent on Sun, 21 Mar 2021 12:01:58 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.12-rc4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5e3ddf96e75983e4c404467fbb61b92d09333a1f
Thank you!
--
Hi Linus,
please pull the freshest pile of shiny x86/urgent fixes for 5.12.
Thx.
---
The following changes since commit 1e28eed17697bcf343c6743f0028cc3b5dd88bf0:
Linux 5.12-rc3 (2021-03-14 14:41:02 -0700)
are available in the Git repository at:
The pull request you sent on Sun, 14 Mar 2021 13:07:26 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.12_rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0a7c10df49eb69dd888ea8b8ddd29bde2aa2fd48
Thank you!
--
Hi Linus,
please pull the accumulated x86/urgent pile for v5.12-rc3.
Thx.
---
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
The pull request you sent on Sun, 14 Feb 2021 11:34:14 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c553021498640050340924bd62fa580e253467ac
Thank you!
--
Hi Linus,
I kinda knew while typing "I hope this is the last batch of x86/urgent
updates" last week, Murphy was reading too and uttered "Hold my beer!".
So here's more fixes... Thanks Murphy.
Anyway, please pull three more x86/urgent fixes for 5.11 final. We
should be finally ready (famous last
On Tue, Feb 9, 2021 at 10:26 AM Andy Lutomirski wrote:
> >
> > Anything else would just be insanely complicated, I feel.
>
> The other model is “don’t do that then.”
Hmm. I guess all the code that does int3 patching could just be taught
to always go to the next instruction instead.
I don't
> On Feb 9, 2021, at 10:09 AM, Linus Torvalds
> wrote:
>
> On Tue, Feb 9, 2021 at 8:55 AM Andy Lutomirski wrote:
>>
>> Or we hack up #CP to handle this case. I don’t quite know how I feel about
>> this.
>
> I think that's the sane model - if we've replaced the instruction with
> 'int3',
On Tue, Feb 9, 2021 at 8:55 AM Andy Lutomirski wrote:
>
> Or we hack up #CP to handle this case. I don’t quite know how I feel about
> this.
I think that's the sane model - if we've replaced the instruction with
'int3', and we end up getting #CP due to that, just do the #BP
handling.
Anything
> On Feb 9, 2021, at 8:45 AM, Alexei Starovoitov
> wrote:
>
> On Tue, Feb 9, 2021 at 6:49 AM Steven Rostedt wrote:
>>
>>> On Tue, 9 Feb 2021 09:32:34 +0100 (CET)
>>> Miroslav Benes wrote:
>>>
>>> powerpc has this
>>>
>>> static inline unsigned long klp_get_ftrace_location(unsigned long
On Tue, Feb 9, 2021 at 6:49 AM Steven Rostedt wrote:
>
> On Tue, 9 Feb 2021 09:32:34 +0100 (CET)
> Miroslav Benes wrote:
>
> > powerpc has this
> >
> > static inline unsigned long klp_get_ftrace_location(unsigned long faddr)
> > {
> > /*
> > * Live patch works only with
On Tue, 9 Feb 2021, Steven Rostedt wrote:
> On Tue, 9 Feb 2021 09:32:34 +0100 (CET)
> Miroslav Benes wrote:
>
> > powerpc has this
> >
> > static inline unsigned long klp_get_ftrace_location(unsigned long faddr)
> >
> > {
On Tue, 9 Feb 2021 09:32:34 +0100 (CET)
Miroslav Benes wrote:
> powerpc has this
>
> static inline unsigned long klp_get_ftrace_location(unsigned long faddr)
>
> {
>
On Mon, 8 Feb 2021, Steven Rostedt wrote:
> On Mon, 8 Feb 2021 16:47:05 +0100
> Peter Zijlstra wrote:
>
> > > /*
> > > * Convert a function address into the appropriate ftrace location.
> > > *
> > > * Usually this is just the address of the function, but on some
> > > architectures
> > >
On Mon, 8 Feb 2021 16:47:05 +0100
Peter Zijlstra wrote:
> > /*
> > * Convert a function address into the appropriate ftrace location.
> > *
> > * Usually this is just the address of the function, but on some
> > architectures
> > * it's more complicated so allow them to provide a custom
On 2/7/2021 2:35 PM, Dave Hansen wrote:
On 2/7/21 12:44 PM, Alexei Starovoitov wrote:
It probably is an item on some Intel manager's to-enable list. So far,
the CET enablement concentrates only on userspace but dhansen might know
more about future plans. CCed.
It's definitely on our radar to
On Mon, Feb 08, 2021 at 09:33:00AM -0600, Josh Poimboeuf wrote:
> On Mon, Feb 08, 2021 at 10:02:06AM -0500, Steven Rostedt wrote:
> > On Sun, 7 Feb 2021 16:45:40 -0600
> > Josh Poimboeuf wrote:
> >
> > > > I do suspect involved people should start thinking about how they want
> > > > to deal
On Mon, Feb 08, 2021 at 10:02:06AM -0500, Steven Rostedt wrote:
> On Sun, 7 Feb 2021 16:45:40 -0600
> Josh Poimboeuf wrote:
>
> > > I do suspect involved people should start thinking about how they want
> > > to deal with functions starting with
> > >
> > > endbr64
> > > call
On Sun, 7 Feb 2021 16:45:40 -0600
Josh Poimboeuf wrote:
> > I do suspect involved people should start thinking about how they want
> > to deal with functions starting with
> >
> > endbr64
> > call __fentry__
> >
> > instead of the call being at the very top of the function.
>
On Sun, Feb 07, 2021 at 10:31:32AM -0800, Andy Lutomirski wrote:
>
> > On Feb 7, 2021, at 10:19 AM, Dave Hansen wrote:
> >
> > On 2/7/21 9:58 AM, Borislav Petkov wrote:
> >>> On Sun, Feb 07, 2021 at 09:49:18AM -0800, Linus Torvalds wrote:
> >>> On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov
On Sun, Feb 07, 2021 at 10:15:49AM -0800, Linus Torvalds wrote:
> On Sun, Feb 7, 2021 at 9:58 AM Borislav Petkov wrote:
> >
> > It probably is an item on some Intel manager's to-enable list. So far,
> > the CET enablement concentrates only on userspace but dhansen might know
> > more about future
On 2/7/21 12:44 PM, Alexei Starovoitov wrote:
>>> It probably is an item on some Intel manager's to-enable list. So far,
>>> the CET enablement concentrates only on userspace but dhansen might know
>>> more about future plans. CCed.
>> It's definitely on our radar to look at after CET userspace.
>
On Sun, Feb 7, 2021 at 10:21 AM Dave Hansen wrote:
>
> On 2/7/21 9:58 AM, Borislav Petkov wrote:
> > On Sun, Feb 07, 2021 at 09:49:18AM -0800, Linus Torvalds wrote:
> >> On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov wrote:
> >>> - Disable CET instrumentation in the kernel so that gcc doesn't
On Sun, Feb 7, 2021 at 10:32 AM Dave Hansen wrote:
>
> My understanding is that AMD has documented support for Shadow Stacks:
>
> https://www.amd.com/system/files/TechDocs/24592.pdf
>
> But has not yet released any documentation about IBT. IBT seems to be
> Intel-only, at least in the
On 2/7/21 10:15 AM, Linus Torvalds wrote:
> On Sun, Feb 7, 2021 at 9:58 AM Borislav Petkov wrote:
>> It probably is an item on some Intel manager's to-enable list. So far,
>> the CET enablement concentrates only on userspace but dhansen might know
>> more about future plans. CCed.
> I think the
> On Feb 7, 2021, at 10:19 AM, Dave Hansen wrote:
>
> On 2/7/21 9:58 AM, Borislav Petkov wrote:
>>> On Sun, Feb 07, 2021 at 09:49:18AM -0800, Linus Torvalds wrote:
>>> On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov wrote:
- Disable CET instrumentation in the kernel so that gcc doesn't
The pull request you sent on Sun, 7 Feb 2021 11:40:22 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.11_rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e24f9c5f6e3127a0679d5ba5575a181b80f219c9
Thank you!
--
On 2/7/21 9:58 AM, Borislav Petkov wrote:
> On Sun, Feb 07, 2021 at 09:49:18AM -0800, Linus Torvalds wrote:
>> On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov wrote:
>>> - Disable CET instrumentation in the kernel so that gcc doesn't add
>>> ENDBR64 to kernel code and thus confuse tracing.
>> So
On Sun, Feb 7, 2021 at 9:58 AM Borislav Petkov wrote:
>
> It probably is an item on some Intel manager's to-enable list. So far,
> the CET enablement concentrates only on userspace but dhansen might know
> more about future plans. CCed.
I think the new Ryzen 5000 series also supports CET, but I
On Sun, Feb 07, 2021 at 09:49:18AM -0800, Linus Torvalds wrote:
> On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov wrote:
> >
> > - Disable CET instrumentation in the kernel so that gcc doesn't add
> > ENDBR64 to kernel code and thus confuse tracing.
>
> So this is clearly the right thing to do
On Sun, Feb 7, 2021 at 2:40 AM Borislav Petkov wrote:
>
> - Disable CET instrumentation in the kernel so that gcc doesn't add
> ENDBR64 to kernel code and thus confuse tracing.
So this is clearly the right thing to do for now, but I wonder if
people have a plan for actually enabling CET and
Hi Linus,
I hope this is the last batch of x86/urgent updates for this round.
Pls pull,
thx.
---
The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04:
Linux 5.11-rc5 (2021-01-24 16:47:14 -0800)
are available in the Git repository at:
The pull request you sent on Sun, 24 Jan 2021 12:02:47 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.11_rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/17b6c49da37f5d57d76bf352d32b0ac498e7c133
Thank you!
--
Hi Linus,
please pull the collection of x86 urgent fixes for 5.11 accumulated so
far.
Thx.
---
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
The pull request you sent on Sun, 10 Jan 2021 11:34:36 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.11_rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a440e4d7618cbe232e4f96dea805bcb89f79b18c
Thank you!
--
Hi Linus,
as expected, fixes started trickling in after the holidays so please
pull the accumulated pile of x86 urgent fixes for 5.11.
Thx.
---
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the Git
The pull request you sent on Sun, 13 Dec 2020 16:04:02 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-12-13
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ec6f5e0e5ca0764b4bc522c9f9d5abf876a0e3e3
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-12-13
up to: 0d07c0ec4381: x86/kprobes: Fix optprobe to detect INT3 padding correctly
A set of x86 and membarrier fixes:
- Correct a few problems in the x86
The pull request you sent on Sun, 06 Dec 2020 13:11:41 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-12-06
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8100a58044f8f502a53d90af96d6030767df0fbd
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-12-06
up to: 84da009f06e6: x86/sev-es: Use new for_each_insn_prefix() macro to loop
over prefixes bytes
A set of fixes for x86:
- Make the AMD L3 QoS code and
The pull request you sent on Sun, 29 Nov 2020 11:38:44 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.10-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7255a39d24a7960da3a55e840ca5cbed5fcb476f
Thank you!
--
Hi Linus,
please pull a couple of urgent fixes which accumulated this last week.
Thx.
---
The following changes since commit 418baf2c28f3473039f2f7377760bd8f6897ae18:
Linux 5.10-rc5 (2020-11-22 15:36:08 -0800)
are available in the Git repository at:
The pull request you sent on Sun, 22 Nov 2020 11:54:05 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.10-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7d53be55c9d78feb38b29fbcaf77af1343549cf1
Thank you!
--
Hi Linus,
please pull the x86/urgent pile for -rc5.
Thx.
---
The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:
Linux 5.10-rc4 (2020-11-15 16:44:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
The pull request you sent on Sun, 15 Nov 2020 13:00:43 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-11-15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/326fd6db6112534738b5229da538bf426d78c851
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-11-15
up to: ff828729be44: iommu/vt-d: Cure VF irqdomain hickup
A small set of fixes for x86:
- Cure the fallout from the MSI irqdomain overhaul which missed
The pull request you sent on Sun, 08 Nov 2020 15:23:19 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-11-08
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/40be821d627c61ee5beb51d265af372ab29804e4
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-11-08
up to: 801284f97378: x86/platform/uv: Recognize UV5 hubless system identifier
A set of x86 fixes:
- Use SYM_FUNC_START_WEAK in the mem* ASM functions
The pull request you sent on Sun, 01 Nov 2020 13:56:04 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-11-01
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7b56fbd83e261484da43f04090bce07570bd117f
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-11-01
up to: cb05143bdf42: x86/debug: Fix DR_STEP vs ptrace_get_debugreg(6)
Three fixes all related to #DB:
- Handle the BTF bit correctly so it doesn't get
The pull request you sent on Tue, 27 Oct 2020 20:14:59 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-10-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ed8780e3f2ecc82645342d070c6b4e530532e680
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-10-27
up to: abee7c494d8c: x86/alternative: Don't call text_poke() in lazy TLB mode
A couple of x86 fixes which missed rc1 due to my stupidity:
- Drop lazy
On Sun, Oct 25 2020 at 11:34, Linus Torvalds wrote:
> On Sun, Oct 25, 2020 at 7:25 AM Thomas Gleixner wrote:
>>
>> Restore the original #DE Oops message so tools which parse crash or dmesg
>> find what they expect.
>
> Hmm. I already got this one from Borislav as a different commit
>
On Sun, Oct 25, 2020 at 7:25 AM Thomas Gleixner wrote:
>
> Restore the original #DE Oops message so tools which parse crash or dmesg
> find what they expect.
Hmm. I already got this one from Borislav as a different commit
(5f1ec1fd3225: "x86/traps: Fix #DE Oops message regression"), so I'm
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-10-25
up to: 20802fef73a5: x86/traps: Fix #DE Oops message regression
Restore the original #DE Oops message so tools which parse crash or dmesg
find what they
The pull request you sent on Tue, 13 Oct 2020 19:36:15 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.10-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/857d64485e7c920364688a8a6dd0ffe5774327b6
Thank you!
--
Hi Linus,
here's the clang build warning fix from yesterday which is finally
ready. I've added a second one from the tip's urgent queue which could
go in now too.
Please pull,
thx.
---
The following changes since commit 8b6591fd0ac8b7e8b2873703bc24b71a6f3d2d3e:
Merge tag
The pull request you sent on Sun, 27 Sep 2020 15:06:53 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-09-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f8818559ca6251adbcd9408dc1ebe3b832f3e1d7
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-09-27
up to: 86a82ae0b509: x86/ioapic: Unbreak check_timer()
Two fixes for the x86 interrupt code:
- Unbreak the magic 'search the timer interrupt' logic in
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-09-27
up to: 86a82ae0b509: x86/ioapic: Unbreak check_timer()
Two fixes for the x86 interrupt code:
- Unbreak the magic 'search the timer interrupt' logic in
The pull request you sent on Sun, 20 Sep 2020 21:23:15 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.9_rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/217eee7231e4b70995bfc24d279c61f6fefbf5d6
Thank you!
--
Hi Linus,
please pull the x86/urgent pile accumulated so far.
Thx.
---
The following changes since commit f4d51dffc6c01a9e94650d95ce0104964f8ae822:
Linux 5.9-rc4 (2020-09-06 17:11:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
On Sun, Aug 30 2020 at 12:13, Linus Torvalds wrote:
> On Sun, Aug 30, 2020 at 11:04 AM Thomas Gleixner wrote:
>>
>>The historical inconsistent for_each_cpu() behaviour of
>>ignoring the cpumask and unconditionally claiming that CPU0 is in the
>>mask struck again. Sigh.
>
> I guess we
The pull request you sent on Sun, 30 Aug 2020 18:03:39 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-08-30
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dcc5c6f013d841e9ae74d527d312d512dfc2e2f0
Thank you!
--
Deet-doot-dot, I
On Sun, Aug 30, 2020 at 11:04 AM Thomas Gleixner wrote:
>
>The historical inconsistent for_each_cpu() behaviour of
>ignoring the cpumask and unconditionally claiming that CPU0 is in the
>mask struck again. Sigh.
I guess we could remove the UP optimizations these days. It's not like
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-08-30
up to: 784a0830377d: genirq/matrix: Deal with the sillyness of for_each_cpu()
on UP
Three interrupt related fixes for X86:
- Move disabling of the local
On Sun, Aug 23, 2020 at 3:35 PM Linus Torvalds
wrote:
>
> On Sun, Aug 23, 2020 at 3:27 PM Andy Lutomirski wrote:
> >
> > Every interrupt is going to load the CS and SS descriptor cache lines.
>
> Yeah, but this isn't even sharing the same GDT cache line. Those two
> are at least in the same
On Sun, Aug 23, 2020 at 3:27 PM Andy Lutomirski wrote:
>
> Every interrupt is going to load the CS and SS descriptor cache lines.
Yeah, but this isn't even sharing the same GDT cache line. Those two
are at least in the same cacheline, and hey, that is forced upon us by
the architecture, so we
On Sun, Aug 23, 2020 at 3:01 PM Thomas Gleixner wrote:
>
> > And I don't think we need the GDT for anything else normally, so it's
> > not even going to be cached.
>
> Who cares, really?
>
> It's pretty irrelevant because the main source of horrors are in having
> to run through _ALL_ registered
On Sun, Aug 23, 2020 at 11:29 AM Linus Torvalds
wrote:
>
> On Sun, Aug 23, 2020 at 1:26 AM Thomas Gleixner wrote:
> >
> > Remove the RDPID optimization, which is not even
> > backed by numbers from the paranoid entry path instead.
>
> Ugh, that's sad. I'd expect the LSL to be quite a bit slower
On Sun, Aug 23 2020 at 11:29, Linus Torvalds wrote:
> On Sun, Aug 23, 2020 at 1:26 AM Thomas Gleixner wrote:
>>
>> Remove the RDPID optimization, which is not even
>> backed by numbers from the paranoid entry path instead.
>
> Ugh, that's sad. I'd expect the LSL to be quite a bit slower than the
The pull request you sent on Sun, 23 Aug 2020 08:25:37 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-08-23
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/550c2129d93d5eb198835ac83c05ef672e8c491c
Thank you!
--
Deet-doot-dot, I
On Sun, Aug 23, 2020 at 1:26 AM Thomas Gleixner wrote:
>
> Remove the RDPID optimization, which is not even
> backed by numbers from the paranoid entry path instead.
Ugh, that's sad. I'd expect the LSL to be quite a bit slower than the
RDPID on raw hardware, since LSL has to go out to the GDT.
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-08-23
up to: 6a3ea3e68b8a: x86/entry/64: Do not use RDPID in paranoid entry to
accomodate KVM
A single fix for x86 which removes the RDPID usage from the
The pull request you sent on Sun, 19 Jul 2020 13:18:13 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-07-19
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/efb9666e900b6f8f079adb2ab18a7be266434cd3
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-07-19
up to: da05b143a308: x86/boot: Don't add the EFI stub to targets
A pile of fixes for x86:
- Fix the I/O bitmap invalidation on XEN PV, which was
--Andy
> On Jul 5, 2020, at 12:46 PM, Linus Torvalds
> wrote:
>
> On Sun, Jul 5, 2020 at 8:47 AM Thomas Gleixner wrote:
>>
>> - Disable 16 bit segments on XEN PV. It's not supported because XEN PV
>> does not implement ESPFIX64
>
> I don't disagree with this conceptually, and I've
The pull request you sent on Sun, 05 Jul 2020 15:46:56 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-07-05
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/72674d480076067d627e708c0a062dd900438bd7
Thank you!
--
Deet-doot-dot, I
On Sun, Jul 5, 2020 at 8:47 AM Thomas Gleixner wrote:
>
> - Disable 16 bit segments on XEN PV. It's not supported because XEN PV
>does not implement ESPFIX64
I don't disagree with this conceptually, and I've pulled it, but
christ, that warning is over-engineered.
Seriously, it uses a mutex
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-07-05
up to: cc801833a171: x86/ldt: Disable 16-bit segments on Xen PV
A series of fixes for x86:
- Reset MXCSR in kernel_fpu_begin() to prevent using a stale
The pull request you sent on Sun, 28 Jun 2020 16:43:19 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_5.8_rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/098c7938217dfd5ef61720bb93d08cc836274b55
Thank you!
--
Hi Linus,
please pull the x86/urgent pile which has nothing but clear fixes.
Thx.
---
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
The pull request you sent on Thu, 11 Jun 2020 18:46:23 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-06-11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6a45a65888393eda692fce0851c40d9f5ce4ef66
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-06-11
up to: 7778d8417b74: x86/vdso: Unbreak paravirt VDSO clocks
A set of fixes and updates for x86:
- Unbreak paravirt VDSO clocks. While the VDSO code was
The pull request you sent on Sun, 31 May 2020 13:58:42 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-05-31
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8fc984aedcedbbabae91d8496bd0b608c0749a98
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-05-31
up to: aa61b7bb00f7: Merge branch 'fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs into x86/urgent
A pile of x86 fixes:
- Prevent a
The pull request you sent on Sun, 24 May 2020 15:08:03 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-05-24
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/667b6249b71c30c20fcd2f312f1665d90348635a
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-05-24
up to: 187b96db5ca7: x86/unwind/orc: Fix unwind_get_return_address_ptr() for
inactive tasks
Two fixes for x86:
- Unbreak stack dumps for inactive
The pull request you sent on Sun, 17 May 2020 11:04:04 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.7-rc7
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/43567139f5f3808cda4f61c956576f8a4f2232cb
Thank you!
--
Hi Linus,
as promised, please pull a single fix for kernels built with gcc10 and
stack protector enabled.
Thx.
---
The following changes since commit 2ef96a5bb12be62ef75b5828c0aab838ebb29cb8:
Linux 5.7-rc5 (2020-05-10 15:16:58 -0700)
are available in the Git repository at:
The pull request you sent on Sun, 10 May 2020 11:55:59 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-05-10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c14cab2688d09b851349acbb83e5fce8e0d4ca42
Thank you!
--
Deet-doot-dot, I
Linus,
please pull the latest x86/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-2020-05-10
up to: fb9cbbc895eb: x86/unwind/orc: Move ORC sorting variables under
!CONFIG_MODULES
A set of fixes for x86:
- Ensure that direct mapping alias is
The pull request you sent on Sun, 20 Oct 2019 10:13:56 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4fe34d61a3a9d9ed954cbc90713506a7598d6b36
Thank you!
--
Deet-doot-dot, I am
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
up to: 228d120051a2: x86/boot/acpi: Move get_cmdline_acpi_rsdp() under #ifdef
guard
A small set of x86 fixes:
- Prevent a NULL pointer
The pull request you sent on Sun, 01 Sep 2019 06:07:33 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9f159ae07f07fc540290f21937231034f554bdd7
Thank you!
--
Deet-doot-dot, I am
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
up to: 7af0145067bc: x86/mm/cpa: Prevent large page split when ftrace flips RW
on kernel text
A set of fixes for x86:
- Fix the bogus
On Wed, Aug 28, 2019 at 05:20:41PM +0200, David Sterba wrote:
> On Tue, Aug 27, 2019 at 07:39:55PM +0200, Borislav Petkov wrote:
> > @@ -42,5 +43,24 @@ void x86_init_rdrand(struct cpuinfo_x86 *c)
> > return;
> > }
> > }
> > +
> > + /*
> > +* Stupid
On Tue, Aug 27, 2019 at 07:39:55PM +0200, Borislav Petkov wrote:
> @@ -42,5 +43,24 @@ void x86_init_rdrand(struct cpuinfo_x86 *c)
> return;
> }
> }
> +
> + /*
> + * Stupid sanity-check whether RDRAND does *actually* generate
> + * some at
1 - 100 of 129 matches
Mail list logo
