The pull request you sent on Sun, 28 Mar 2021 12:44:42 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2021-03-28
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/36a14638f7c06546717cc1316fcfee6da42b98cc
Thank you!
--
Deet-doot-dot, I
Linus,
On Sun, Oct 11 2020 at 11:00, Linus Torvalds wrote:
> On Sun, Oct 11, 2020 at 1:09 AM Ingo Molnar wrote:
>>
>> - Fix a (hopefully final) IRQ state tracking bug vs. MCE handling
>
> Why is the nmi_enter/nmi_exit thing not a problem on non-x86 architectures?
>
> Put another way: x86 does ex
The pull request you sent on Sun, 11 Oct 2020 10:08:59 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-10-11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c120ec12e216225f7536cc1b924fe428ff64b5bd
Thank you!
--
Deet-doot-dot, I
On Sun, Oct 11, 2020 at 1:09 AM Ingo Molnar wrote:
>
> - Fix a (hopefully final) IRQ state tracking bug vs. MCE handling
Why is the nmi_enter/nmi_exit thing not a problem on non-x86 architectures?
Put another way: x86 does extra work to track IRQ state across NMI.
What makes x86 special? It _fe
The pull request you sent on Sun, 6 Sep 2020 10:15:15 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-09-06
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/015b3155c46a089f623c8a2e794ffad84143565d
Thank you!
--
Deet-doot-dot, I a
The pull request you sent on Sat, 15 Aug 2020 13:45:52 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-08-15
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/50f6c7dbd973092d8e5f3c89f29eb4bea19fdebd
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sat, 25 Jul 2020 13:46:37 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-2020-07-25
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fbe0d451bcea569fc0ed3455511a90646c8a9c81
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sat, 12 Oct 2019 15:19:16 +0200:
> 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/7a275fd7b9519b5cc63270a8964055aadb04de26
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 12 Sep 2019 14:57:10 +0200:
> 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/95217783b7f6f331e7a6675e0a31fb9a5a1b9a36
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 5 Sep 2019 10:07:19 +0200:
> 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/19e4147a04a43d210dbacda76e0988f90bb0ba45
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 29 Jun 2019 11:14:07 +0200:
> 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/728254541ebcc7fee869c3c4c3f36f96be791edb
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 16 Jun 2019 11:29:52 -:
> 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/963172d9c7e862654d3d24cbcafb33f33ae697a8
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 2 Jun 2019 19:44:42 +0200:
> 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/7bd1d5edd0160b615ab8748cf94dabcab1fb01cb
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 16 May 2019 18:26:16 +0200:
> 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/d396360acdf7e57edcd9e2d080343b0353d65d63
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 27 Apr 2019 16:42:56 +0200:
> 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/037904a22bf8b2c999a6e2a8ba971b549c1e9600
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 20 Apr 2019 09:38:09 +0200:
> 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/1fd91d719eb1ae83ef500eb4148d11db9db39a41
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 12 Apr 2019 15:10:42 +0200:
> 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/6d0a598489ca687e1ebac37eef546526eca41347
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 10 Mar 2019 12:33:54 +0100:
> 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/262d6a9a63a387c8dfa9eb4f7713e159c941e52c
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sat, 2 Mar 2019 20:19:57 +0100 (CET):
> 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/e7c42a89e9f16039684418dfe3c43b068734ff8f
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Sun, 17 Feb 2019 11:19:08 +0100:
> 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/8d33316d520501f24fef180ea5b860ecb9e64506
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 10 Feb 2019 10:13:40 +0100:
> 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/aadaa8061189a9e5d8a1327b328453d663e8cbc9
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 11 Jan 2019 08:14:54 +0100:
> 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/e8af37f3f488e7adce2b5c6f6dfe8c83c2662e1f
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 21 Dec 2018 13:25:45 +0100:
> 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/70ad6368e878857db315788dab36817aa992c86a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 9 Dec 2018 23:06:55 +0100:
> 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/8586ca8a214471e4573d76356aabe890bfecdc8a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 30 Nov 2018 07:29:06 +0100:
> 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/1ec63573b2db363848abb313cc75eb29e9abc1b3
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 11 Nov 2018 09:11:09 +0100:
> 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/b6df7b6db1c1837fc9eada74ed561cbfe7746755
Thank you!
--
Deet-doot-dot, I am a
On Sat, Nov 3, 2018 at 4:09 PM Ingo Molnar wrote:
>
> A number of fixes and some late updates:
Pulled,
Linus
On Sat, Oct 20, 2018 at 10:54:25AM +0200, Ingo Molnar wrote:
> Greg,
>
> 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
Now merged, thanks.
greg k-h
On Thu, Oct 11, 2018 at 11:14:16AM +0200, Ingo Molnar wrote:
> Greg,
>
> 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
Now merged, thanks.
greg k-h
On Fri, Oct 05, 2018 at 11:53:54AM +0200, Ingo Molnar wrote:
> Greg,
>
> 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
Now merged, thanks.
greg k-h
On Sat, Sep 22, 2018 at 02:34:06PM +0200, Thomas Gleixner wrote:
> Greg,
>
> 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
Now pulled, thanks.
greg k-h
* Linus Torvalds wrote:
> On Mon, Jul 2, 2018 at 11:48 AM Andy Lutomirski wrote:
> >
> > BTR is way more leet than AND!
>
> I stand corrected.
Ok, on that basis I won't try to convert it to AND ;-)
Seriously though, there's two other 32-bit prefix cleanup/micro-speedup changes
I'll queue u
On Mon, Jul 2, 2018 at 11:48 AM Andy Lutomirski wrote:
>
> BTR is way more leet than AND!
I stand corrected.
Linus
On Sat, Jun 30, 2018 at 12:01 PM, Linus Torvalds
wrote:
> On Sat, Jun 30, 2018 at 1:49 AM Ingo Molnar wrote:
>>
>> --- a/arch/x86/entry/entry_32.S
>> +++ b/arch/x86/entry/entry_32.S
>> @@ -477,7 +477,7 @@ ENTRY(entry_SYSENTER_32)
>> * whereas POPF does not.)
>> */
>> add
On Sat, Jun 30, 2018 at 1:49 AM Ingo Molnar wrote:
>
> --- a/arch/x86/entry/entry_32.S
> +++ b/arch/x86/entry/entry_32.S
> @@ -477,7 +477,7 @@ ENTRY(entry_SYSENTER_32)
> * whereas POPF does not.)
> */
> addl$PT_EFLAGS-PT_DS, %esp /* point esp at pt_regs->flags */
> -
On Sun, 22 Apr 2018, Linus Torvalds wrote:
> On Sun, Apr 22, 2018 at 4:04 AM, Thomas Gleixner wrote:
> >
> > A small set of fixes for x86:
>
> Hmm. Not the fixes for the global bit problems that caused a couple of
> pretty bad issues?
>
> I realize that they wanted testing, but considering how
On Sun, Apr 22, 2018 at 4:04 AM, Thomas Gleixner wrote:
>
> A small set of fixes for x86:
Hmm. Not the fixes for the global bit problems that caused a couple of
pretty bad issues?
I realize that they wanted testing, but considering how bad the
current situation is...
Linus
On Sun, 4 Mar 2018, Linus Torvalds wrote:
> On Sun, Mar 4, 2018 at 11:40 AM, Linus Torvalds
> wrote:
> > On Sun, Mar 4, 2018 at 7:02 AM, Thomas Gleixner wrote:
> >>
> >> please pull the latest x86-urgent-for-linus git tree from:
> >>
> >>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.
On Sun, Mar 4, 2018 at 11:40 AM, Linus Torvalds
wrote:
> On Sun, Mar 4, 2018 at 7:02 AM, Thomas Gleixner wrote:
>>
>> 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
>
> Nothing there.
>
> Did y
On Sun, Mar 4, 2018 at 7:02 AM, Thomas Gleixner wrote:
>
> 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
Nothing there.
Did you forget to push out?
Linus
On Thu, 18 Jan 2018 01:24:08 +0100 Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Wed, Jan 17, 2018 at 7:41 AM, Ingo Molnar wrote:
> > >
> > > - A kdump fix
> > >
> > > out-of-topic modifications in x86-urgent-for-linus:
> > >
* Linus Torvalds wrote:
> On Wed, Jan 17, 2018 at 7:41 AM, Ingo Molnar wrote:
> >
> > - A kdump fix
> >
> > out-of-topic modifications in x86-urgent-for-linus:
> > -
> > include/linux/crash_core.h # 9f15b9120f56: kdump: Write th
On Wed, Jan 17, 2018 at 7:41 AM, Ingo Molnar wrote:
>
> - A kdump fix
>
> out-of-topic modifications in x86-urgent-for-linus:
> -
> include/linux/crash_core.h # 9f15b9120f56: kdump: Write the correct
> add
> kernel/crash_core.c
On Sun, 31 Dec 2017, Linus Torvalds wrote:
> On Sun, Dec 31, 2017 at 1:09 PM, Linus Torvalds
> wrote:
> > On Sun, Dec 31, 2017 at 8:32 AM, Thomas Gleixner wrote:
> >>
> >>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> >> x86-urgent-for-linus
> >
> > This doesn't contain what you
On Sun, 31 Dec 2017, Linus Torvalds wrote:
> On Sun, Dec 31, 2017 at 8:32 AM, Thomas Gleixner wrote:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > x86-urgent-for-linus
>
> This doesn't contain what you claim it does, it's old x86 fixes from
> two weeks ago.
>
> Forgo
On Sun, Dec 31, 2017 at 1:09 PM, Linus Torvalds
wrote:
> On Sun, Dec 31, 2017 at 8:32 AM, Thomas Gleixner wrote:
>>
>>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>> x86-urgent-for-linus
>
> This doesn't contain what you claim it does, it's old x86 fixes from
> two weeks ago.
>
On Sun, Dec 31, 2017 at 8:32 AM, Thomas Gleixner wrote:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-urgent-for-linus
This doesn't contain what you claim it does, it's old x86 fixes from
two weeks ago.
Forgot to push out?
Linus
On Sun, Dec 17, 2017 at 12:41:42PM +0100, Thomas Gleixner wrote:
> > X86_BUG_CPU_SECURE_MODE_PTI should be added to DISABLED_FEATURES or
> > DISABLED_BUGS or whatever if it's not configured in, which will reduce
> > bloat. Borislav, that's kind of up your alley, since I don't think
> > the appropr
On Sat, 16 Dec 2017, Andy Lutomirski wrote:
> On Fri, Dec 15, 2017 at 8:07 AM, Ingo Molnar wrote:
> I few things I noticed in the PTI tree:
>
> "x86/mm/pti: Map ESPFIX into user space" has a leftover pr_err().
> Sorry, my bad, I've spent *way* too long looking at this crap to
> retain my sanity.
* Andy Lutomirski wrote:
> > Is this tree looking good to you standalone?
>
> I think this stuff is looking okay, although I'm a bit mystified by
> the whole merge base thing. But if the backporters and Linus like it,
> then whatever.
To explain the merge base thing: considering that v4.14 is
On Fri, Dec 15, 2017 at 8:07 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> On Fri, Dec 15, 2017 at 7:43 AM, Ingo Molnar wrote:
>> > Linus,
>>
>> >
>> > - two 5-level paging related fixes
>>
>> Which reminds me: can you grab this one, too?
>>
>> https://lkml.kernel.org/r/24c898b4f44fd
* Andy Lutomirski wrote:
> On Fri, Dec 15, 2017 at 7:43 AM, Ingo Molnar wrote:
> > Linus,
>
> >
> > - two 5-level paging related fixes
>
> Which reminds me: can you grab this one, too?
>
> https://lkml.kernel.org/r/24c898b4f44fdf8c22d93703850fb384ef87cfdc.1513035461.git.l...@kernel.org
Yea
On Fri, Dec 15, 2017 at 7:43 AM, Ingo Molnar wrote:
> Linus,
>
> - two 5-level paging related fixes
Which reminds me: can you grab this one, too?
https://lkml.kernel.org/r/24c898b4f44fdf8c22d93703850fb384ef87cfdc.1513035461.git.l...@kernel.org
On Sat, 25 Jun 2016, Linus Torvalds wrote:
> I'm pretty sure that's not the final fix. And that it caused more
> problems than it fixed, afaik.
Sorry. That slipped through my attention. Thanks for spotting it!
tglx
On Sun, Jun 26, 2016 at 02:45:44AM +0200, Rafael J. Wysocki wrote:
> The (hopefully) final one is https://patchwork.kernel.org/patch/9189139/
> and it still is pending a test on the Boris' machine where the previous one
> didn't work. If that doesn't pass, we'll need to defer it until we know
> th
On Saturday, June 25, 2016 06:49:09 AM Linus Torvalds wrote:
> On Sat, Jun 25, 2016 at 1:25 AM, Thomas Gleixner wrote:
> >
> > please pull the latest x86-urgent-for-linus git tree from:
>
> Nope.
>
> > This update contains:
> >
> > - The final fix for the hibernation resume path which addresse
On Sat, Jun 25, 2016 at 1:25 AM, Thomas Gleixner wrote:
>
> please pull the latest x86-urgent-for-linus git tree from:
Nope.
> This update contains:
>
> - The final fix for the hibernation resume path which addresses the observed
> crashes which were exposed by a recent change which sets N
Linus
On Sun, 13 Dec 2015, Thomas Gleixner wrote:
> 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
>
> A series of small fixes to plug a race condition in the x86 vector
> management
On Sat, 3 Oct 2015, Ingo Molnar wrote:
> > 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
> >
> ># HEAD: f4b4aae1828855db761bf998ce37d3062b1d6446 x86/headers/uapi: Fix
> > __BITS_PER_LO
* Ingo Molnar wrote:
> 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
>
># HEAD: f4b4aae1828855db761bf998ce37d3062b1d6446 x86/headers/uapi: Fix
> __BITS_PER_LONG value for x32
On 08/19/2015 08:50 AM, Ingo Molnar wrote:
> I get some instances of:
>
>/etc/rc3.d/S99local: line 26: 1626 Illegal instruction
>
> due to user-space presuming modern FPU capabilities:
>
> Program received signal SIGILL, Illegal instruction.
>
Yes, and MMX, SSE et al didn't have the envision trap support, so you would
have to do a full decide and emulation inside the #UD handler. However, the
trap overhead for a lot of those instructions is extreme, as compared to the
rather heavyweight x87 instructions (in terms of the ratio between
On Wed, Aug 19, 2015 at 3:00 AM, H. Peter Anvin wrote:
>
> And I bet if CPUID actually reported the right thing it probably would work
> okay. As I said, I tested this under Qemu which reported an accurate (lack
> of) CPUID for a 486SX.
While I agree that cpuid is a problem for FPU emulation on
On 08/18/2015 11:50 PM, Ingo Molnar wrote:
>
> So I take back my claim, math-emu works. If math-emu grew support for some P6
> era
> FPU instructions it might even boot up generic distros without too much
> trouble.
>
For the record, I used a RedHat 4.1 (not Fedora or RHEL!) userspace.
http
On 08/18/15 23:50, Ingo Molnar wrote:
Ah, so I was able to make math-emu work with the 'no387 nofxsr' boot options.
It turns out that the crash happens due 'no387' not turning off all modern FPU
features in cpufeatures, which confuses the FPU code. (This is a far less severe
bug than math emu n
* Ingo Molnar wrote:
>
> * H. Peter Anvin wrote:
>
> > On 08/17/2015 10:17 AM, Linus Torvalds wrote:
> > > On Mon, Aug 17, 2015 at 9:58 AM, H. Peter Anvin wrote:
> > >>
> > >> That is not true. It *does* work, and I have tested it fairly recently.
> > >
> > > Ok, so it's not too badly brok
* Ingo Molnar wrote:
> So I went and built 743aa456c1834f76 with ARCH=i386 defconfig
> +MATH_EMULATION=y
> and booted it on real hardware with and without 'no387':
>
> - 743aa456c1834f76: boots fine to a generic distro
> - 743aa456c1834f76 + no387: early crash
>
> the early crash
* H. Peter Anvin wrote:
> On 08/17/2015 10:17 AM, Linus Torvalds wrote:
> > On Mon, Aug 17, 2015 at 9:58 AM, H. Peter Anvin wrote:
> >>
> >> That is not true. It *does* work, and I have tested it fairly recently.
> >
> > Ok, so it's not too badly broken. Good.
> >
> > Also, while it's been a
* Linus Torvalds wrote:
> On Mon, Aug 17, 2015 at 3:59 AM, Denys Vlasenko wrote:
> >
> > I have it running linux 2.6.20 and busybox here:
> >
> > http://busybox.net/live_bbox/live_bbox.html
> >
> > (or rather, *you* will have it running linux 2.6.20 inside your browser,
> > after you click on t
* Andy Lutomirski wrote:
> On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>
> > So when I re-introduced static allocations math-emu started working again,
> > to
> > a limited degree: on a modern distro, trying to boot /bin/bash I got a
> > prompt,
> > but various programs would segfau
I should make it clear: I was using a 486SX model in Qemu.
On August 17, 2015 5:19:10 PM PDT, Andy Lutomirski wrote:
>On Mon, Aug 17, 2015 at 5:06 PM, H. Peter Anvin wrote:
>> User space does not need to treat for FPU instructions, except for
>performance reasons, because the kernel emulates the
I used a very old userspace, and embedded systems are much more likely to use
uclibc than glibc. However, if they try to use SSE without checking they will
break on a hell of a lot more hardware.
On August 17, 2015 5:19:10 PM PDT, Andy Lutomirski wrote:
>On Mon, Aug 17, 2015 at 5:06 PM, H. Pet
On Mon, Aug 17, 2015 at 5:06 PM, H. Peter Anvin wrote:
> User space does not need to treat for FPU instructions, except for
> performance reasons, because the kernel emulates the full x87 FPU. So it is
> localized to the kernel.
But user space needs to avoid SSE2 and such, I suspect. In gener
User space does not need to treat for FPU instructions, except for performance
reasons, because the kernel emulates the full x87 FPU. So it is localized to
the kernel.
On August 17, 2015 4:59:18 PM PDT, Andy Lutomirski wrote:
>On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>> So when I r
I ran a hacked Qemu with FPU off.
On August 17, 2015 4:59:18 PM PDT, Andy Lutomirski wrote:
>On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>> So when I re-introduced static allocations math-emu started working
>again, to a
>> limited degree: on a modern distro, trying to boot /bin/bash I g
On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
> So when I re-introduced static allocations math-emu started working again, to
> a
> limited degree: on a modern distro, trying to boot /bin/bash I got a prompt,
> but
> various programs would segfault. I did not investigate it any deeper, I
On 17/08/15 18:17, Linus Torvalds wrote:
On Mon, Aug 17, 2015 at 9:58 AM, H. Peter Anvin wrote:
That is not true. It *does* work, and I have tested it fairly recently.
Ok, so it's not too badly broken. Good.
Also, while it's been a long time since we needed FPU emulation on the
i486sx, I do
On 08/17/2015 10:17 AM, Linus Torvalds wrote:
> On Mon, Aug 17, 2015 at 9:58 AM, H. Peter Anvin wrote:
>> That is not true. It *does* work, and I have tested it fairly recently.
>
> Ok, so it's not too badly broken. Good.
>
> Also, while it's been a long time since we needed FPU emulation on th
Let me see when I last treated this... but I thought it was much more recently
than that.
On August 17, 2015 1:01:43 AM PDT, Ingo Molnar wrote:
>
>(Sorry about the late reply, wasn't around on the weekend.)
>
>* Linus Torvalds wrote:
>
>> Now that said, I doubt anybody cares. Since we don't sup
On Mon, Aug 17, 2015 at 9:58 AM, H. Peter Anvin wrote:
> That is not true. It *does* work, and I have tested it fairly recently.
Ok, so it's not too badly broken. Good.
Also, while it's been a long time since we needed FPU emulation on the
i486sx, I don't recall the details of any of the (much
That is not true. It *does* work, and I have tested it fairly recently.
On August 17, 2015 9:47:01 AM PDT, Linus Torvalds
wrote:
>On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>>
>> Any objections against removing all of math-emu in v4.3? This would
>simplify the
>> FPU code in various p
On Mon, Aug 17, 2015 at 3:59 AM, Denys Vlasenko wrote:
>
> I have it running linux 2.6.20 and busybox here:
>
> http://busybox.net/live_bbox/live_bbox.html
>
> (or rather, *you* will have it running linux 2.6.20 inside your browser,
> after you click on that link)
Heh. I'm not sure that's a very
On Mon, Aug 17, 2015 at 1:01 AM, Ingo Molnar wrote:
>
> Any objections against removing all of math-emu in v4.3? This would simplify
> the
> FPU code in various places beyond math-emu/.
Hmm. I guess we could just try. The fact that you argue that the FP
emulation likely hasn't worked for a few y
On 08/17/2015 10:01 AM, Ingo Molnar wrote:
>
> (Sorry about the late reply, wasn't around on the weekend.)
>
> * Linus Torvalds wrote:
>
>> Now that said, I doubt anybody cares. Since we don't support the original
>> 80386,
>> the only way to ever trigger FP emulation is by having a 486SX or
(Sorry about the late reply, wasn't around on the weekend.)
* Linus Torvalds wrote:
> Now that said, I doubt anybody cares. Since we don't support the original
> 80386,
> the only way to ever trigger FP emulation is by having a 486SX or possibly a
> couple of even rarer clone chips. [...]
Y
On Fri, Aug 14, 2015 at 12:18 PM, Andy Lutomirski wrote:
>
> Unless I'm missing something, it's literally a one-line fix -- just
> put the missing PM_REG_(segment) back in.
Please use address->selector instead. Which should get the fs case right too.
Linus
--
To unsubscribe from t
On Fri, Aug 14, 2015 at 12:06 PM, Linus Torvalds
wrote:
> On Fri, Aug 14, 2015 at 11:57 AM, Linus Torvalds
> wrote:
>>
>> That code seems fine to me (and explicitly errors out when it's not in
>> the LDT). FPU_CS is actually the CS selector value.
>>
>> So testing that for being in the LDT by che
On Fri, Aug 14, 2015 at 11:57 AM, Linus Torvalds
wrote:
> On Fri, Aug 14, 2015 at 11:46 AM, Andy Lutomirski wrote:
>>
>> I think it's only slightly broken.
>>
>> This bit:
>>
>> if ((FPU_CS & 4) != 4) {/* Must be in the LDT */
>> /* Can only handle segmented addressing via
On Fri, Aug 14, 2015 at 11:57 AM, Linus Torvalds
wrote:
>
> That code seems fine to me (and explicitly errors out when it's not in
> the LDT). FPU_CS is actually the CS selector value.
>
> So testing that for being in the LDT by checking bit #2, and then
> using FPU_get_ldt_descriptor() on it actu
On Fri, Aug 14, 2015 at 11:46 AM, Andy Lutomirski wrote:
>
> I think it's only slightly broken.
>
> This bit:
>
> if ((FPU_CS & 4) != 4) {/* Must be in the LDT */
> /* Can only handle segmented addressing via the LDT
>for now, and it must be 16 bit */
>
On Fri, Aug 14, 2015 at 11:25 AM, Linus Torvalds
wrote:
> On Fri, Aug 14, 2015 at 12:15 AM, Ingo Molnar wrote:
>>
>> Please pull the latest x86-urgent-for-linus git tree from:
>
> Nope. It seems to be an unmitigated disaster, as far as I can tell.
>
>> +static inline struct desc_struct FPU_get_ld
On Fri, Aug 14, 2015 at 12:15 AM, Ingo Molnar wrote:
>
> Please pull the latest x86-urgent-for-linus git tree from:
Nope. It seems to be an unmitigated disaster, as far as I can tell.
> +static inline struct desc_struct FPU_get_ldt_descriptor(unsigned seg)
> +{
> + static struct desc_struc
On Sat, Jul 18, 2015 at 05:18:10AM +0200, Ingo Molnar wrote:
> 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
>
># HEAD: 5aaeb5c01c5b6c0be7b7aadbf3ace9f3a4458c3d x86/fpu, sched: In
Ugh, I pulled, but:
On Wed, May 6, 2015 at 5:58 AM, Ingo Molnar wrote:
>
> Ingo Molnar (1):
> x86/mm: Clean up types in xlate_dev_mem_ptr()
>
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index fdf617c00e2f..4bf037b20f47 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86
On Mon, Nov 17, 2014 at 1:21 PM, Markus Trippelsdorf
wrote:
> On 2014.11.17 at 13:02 -0800, Kees Cook wrote:
>>
>> Eek, well, the warning worked, at least (".bss and .brk lack common
>> file offset") since that was kind of an assumption in the script I
>> wanted to make sure we'd catch if it wasn'
On 2014.11.17 at 13:02 -0800, Kees Cook wrote:
>
> Eek, well, the warning worked, at least (".bss and .brk lack common
> file offset") since that was kind of an assumption in the script I
> wanted to make sure we'd catch if it wasn't true.
It depends on the linker being used. gold (my default) tr
On 2014.11.17 at 13:02 -0800, Kees Cook wrote:
> On Mon, Nov 17, 2014 at 5:58 AM, Ingo Molnar wrote:
> >
> > * Markus Trippelsdorf wrote:
> >
> >> On 2014.11.17 at 08:42 +0100, Markus Trippelsdorf wrote:
> >> > On 2014.11.16 at 10:07 +0100, Ingo Molnar wrote:
> >> > >
> >> > > Junjie Mao (1):
> >
On Mon, Nov 17, 2014 at 5:58 AM, Ingo Molnar wrote:
>
> * Markus Trippelsdorf wrote:
>
>> On 2014.11.17 at 08:42 +0100, Markus Trippelsdorf wrote:
>> > On 2014.11.16 at 10:07 +0100, Ingo Molnar wrote:
>> > >
>> > > Junjie Mao (1):
>> > > x86, kaslr: Prevent .bss from overlaping initrd
>> >
* Markus Trippelsdorf wrote:
> On 2014.11.17 at 08:42 +0100, Markus Trippelsdorf wrote:
> > On 2014.11.16 at 10:07 +0100, Ingo Molnar wrote:
> > >
> > > Junjie Mao (1):
> > > x86, kaslr: Prevent .bss from overlaping initrd
> >
> > This breaks the build for me:
> > ...
> > OBJCOPY arch/
On 2014.11.17 at 08:42 +0100, Markus Trippelsdorf wrote:
> On 2014.11.16 at 10:07 +0100, Ingo Molnar wrote:
> >
> > Junjie Mao (1):
> > x86, kaslr: Prevent .bss from overlaping initrd
>
> This breaks the build for me:
> ...
> OBJCOPY arch/x86/boot/compressed/vmlinux.bin
> HOSTCC arch/x
1 - 100 of 177 matches
Mail list logo
