The following commit has been merged into the x86/fpu branch of tip:
Commit-ID: 1ef5423a55c2ac6f1361811efe75b6e46d1023ed
Gitweb:
https://git.kernel.org/tip/1ef5423a55c2ac6f1361811efe75b6e46d1023ed
Author:Mike Hommey
AuthorDate:Tue, 22 Sep 2020 06:56:38 +09:00
Committer
-by: Mike Hommey
---
arch/x86/kernel/cpu/common.c | 55
arch/x86/kernel/fpu/init.c | 55
2 files changed, 55 insertions(+), 55 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index
-by: Mike Hommey
---
arch/x86/kernel/cpu/common.c | 41
arch/x86/kernel/fpu/init.c | 41
2 files changed, 41 insertions(+), 41 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index
FPU initialization handles the clearcpuid command line argument. If it
comes after BSP init, clearcpuid cannot be used to disable features that
trigger some parts of the BSP init code.
Signed-off-by: Mike Hommey
---
arch/x86/kernel/cpu/common.c | 7 ---
1 file changed, 4 insertions(+), 3
On Fri, Oct 03, 2014 at 07:07:58PM +0200, Andrea Arcangeli wrote:
> MADV_USERFAULT is a new madvise flag that will set VM_USERFAULT in the
> vma flags. Whenever VM_USERFAULT is set in an anonymous vma, if
> userland touches a still unmapped virtual address, a sigbus signal is
> sent instead of
On Fri, Oct 03, 2014 at 07:07:58PM +0200, Andrea Arcangeli wrote:
MADV_USERFAULT is a new madvise flag that will set VM_USERFAULT in the
vma flags. Whenever VM_USERFAULT is set in an anonymous vma, if
userland touches a still unmapped virtual address, a sigbus signal is
sent instead of
Hi,
We're running into an interesting issue with Firefox on Android, in
which a segfault signal handler always gets a value of 0 for
siginfo_t.si_addr. The most intesting part is that this only happens on
a few devices/android version combinations. Catching a segfault in gdb
also shows the
Hi,
We're running into an interesting issue with Firefox on Android, in
which a segfault signal handler always gets a value of 0 for
siginfo_t.si_addr. The most intesting part is that this only happens on
a few devices/android version combinations. Catching a segfault in gdb
also shows the
On Fri, Jul 26, 2013 at 09:20:34AM -0400, Jörn Engel wrote:
> On Fri, 26 July 2013 12:01:23 +0400, Vyacheslav Dubeyko wrote:
> >
> > We are discussing not about good or bad idea. We need to elaborate a
> > right solution. I think that suggested idea is not clear. Do you
> > want to support
On Fri, Jul 26, 2013 at 09:20:34AM -0400, Jörn Engel wrote:
On Fri, 26 July 2013 12:01:23 +0400, Vyacheslav Dubeyko wrote:
We are discussing not about good or bad idea. We need to elaborate a
right solution. I think that suggested idea is not clear. Do you
want to support compression in
On Tue, Dec 11, 2012 at 05:11:17PM +0900, Minchan Kim wrote:
> On Tue, Dec 11, 2012 at 08:59:50AM +0100, Mike Hommey wrote:
> > On Tue, Dec 11, 2012 at 04:37:44PM +0900, Minchan Kim wrote:
> > > On Tue, Dec 11, 2012 at 08:17:42AM +0100, Mike Hommey wrote:
> > > > On T
On Tue, Dec 11, 2012 at 04:37:44PM +0900, Minchan Kim wrote:
> On Tue, Dec 11, 2012 at 08:17:42AM +0100, Mike Hommey wrote:
> > On Tue, Dec 11, 2012 at 11:41:04AM +0900, Minchan Kim wrote:
> > > - What's the madvise(addr, length, MADV_VOLATILE)?
> > >
> >
On Tue, Dec 11, 2012 at 04:37:44PM +0900, Minchan Kim wrote:
On Tue, Dec 11, 2012 at 08:17:42AM +0100, Mike Hommey wrote:
On Tue, Dec 11, 2012 at 11:41:04AM +0900, Minchan Kim wrote:
- What's the madvise(addr, length, MADV_VOLATILE)?
It's a hint that user deliver to kernel so kernel
On Tue, Dec 11, 2012 at 05:11:17PM +0900, Minchan Kim wrote:
On Tue, Dec 11, 2012 at 08:59:50AM +0100, Mike Hommey wrote:
On Tue, Dec 11, 2012 at 04:37:44PM +0900, Minchan Kim wrote:
On Tue, Dec 11, 2012 at 08:17:42AM +0100, Mike Hommey wrote:
On Tue, Dec 11, 2012 at 11:41:04AM +0900
On Tue, Dec 11, 2012 at 11:41:04AM +0900, Minchan Kim wrote:
> - What's the madvise(addr, length, MADV_VOLATILE)?
>
> It's a hint that user deliver to kernel so kernel can *discard*
> pages in a range anytime.
>
> - What happens if user access page(ie, virtual address) discarded
> by
On Tue, Dec 11, 2012 at 11:41:04AM +0900, Minchan Kim wrote:
- What's the madvise(addr, length, MADV_VOLATILE)?
It's a hint that user deliver to kernel so kernel can *discard*
pages in a range anytime.
- What happens if user access page(ie, virtual address) discarded
by kernel?
On Fri, Nov 02, 2012 at 09:59:07PM +0100, Michael Kerrisk wrote:
> John,
>
> A question at on one point:
>
> On Wed, Oct 3, 2012 at 12:38 AM, John Stultz wrote:
> > On 10/02/2012 12:39 AM, NeilBrown wrote:
> [...]
> >> The SIGBUS interface could have some merit if it really reduces
> >>
On Fri, Nov 02, 2012 at 09:59:07PM +0100, Michael Kerrisk wrote:
John,
A question at on one point:
On Wed, Oct 3, 2012 at 12:38 AM, John Stultz john.stu...@linaro.org wrote:
On 10/02/2012 12:39 AM, NeilBrown wrote:
[...]
The SIGBUS interface could have some merit if it really reduces
On Fri, Sep 28, 2012 at 11:16:30PM -0400, John Stultz wrote:
> fd based interfaces vs madvise:
> In talking with Taras Glek, he pointed out that for his
> needs, the fd based interface is a little annoying, as it
> requires having to get access to tmpfs file and mmap it in,
>
On Fri, Sep 28, 2012 at 11:16:30PM -0400, John Stultz wrote:
fd based interfaces vs madvise:
In talking with Taras Glek, he pointed out that for his
needs, the fd based interface is a little annoying, as it
requires having to get access to tmpfs file and mmap it in,
On Fri, Feb 22, 2008 at 11:10:48PM -0500, Daniel Barkalow wrote:
> I find that the sequence of changes I make is pretty much unrelated to the
> sequence of changes that end up in the project's history, because my
> changes as I make them involve writing a lot of stubs (so I can build) and
>
On Fri, Feb 22, 2008 at 11:10:48PM -0500, Daniel Barkalow wrote:
I find that the sequence of changes I make is pretty much unrelated to the
sequence of changes that end up in the project's history, because my
changes as I make them involve writing a lot of stubs (so I can build) and
then
22 matches
Mail list logo
