On Thu, Aug 27, 2020 at 2:49 PM Daniel Wagner wrote:
>
> > Would be interesting to see the size numbers for v5.6-rt? Hmm, I'll
> > just start the compiler. It's all scripted anyway :)
>
> v5.6-rt:
>
> -rw-r--r-- 1 wagi users 28688896 Aug 27 13:38 rpi3-image-ll-v5.6.19-rt12
> -rw-r--r-- 1 wagi user
> diff --git a/kernel/futex.c b/kernel/futex.c
> index 69e619baf709..2abe1a0b3062 100644
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -1463,8 +1463,7 @@ static void mark_wake_futex(struct wake_q_head *wake_q,
> struct futex_q *q)
>* Queue the task for later wakeup for after we've rel
On Fri, Jan 11, 2019 at 10:03 PM Thomas Gleixner wrote:
>
> No. The branch was not sent to Linus during the merge window due to holiday
> season induced oversight.
So does it wait for the next merge window now or is it still going to
be sent? This is actually worth stable branches. I've confirmat
Hi Thomas, Ingo, Peter.
I'm wondering, was x86/timers branch of tip tree merged to linus' tree
for v5.0-rc1? Somehow I do not see this patch make it through...
Am I doing something wrong?
--nX
On Tue, Nov 6, 2018 at 9:58 PM tip-bot for Daniel Vacek
wrote:
>
Commit-ID: a786ef152cdcfebc923a67f63c7815806eefcf81
Gitweb: https://git.kernel.org/tip/a786ef152cdcfebc923a67f63c7815806eefcf81
Author: Daniel Vacek
AuthorDate: Mon, 5 Nov 2018 18:10:40 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 6 Nov 2018 21:53:15 +0100
x86/tsc: Make
instead of
simply bailing out unrefined. Usually the next second the readout returns
fast just fine without any issues.
v2: keep using the constant early when the tsc_khz is not available yet
as suggested by tglx
Signed-off-by: Daniel Vacek
---
arch/x86/kernel/tsc.c | 30
On Sat, Nov 3, 2018 at 11:04 AM, Thomas Gleixner wrote:
> Daniel,
>
> On Fri, 2 Nov 2018, Daniel Vacek wrote:
>> On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
>> >> -#define MAX_RETRIES 5
>> >> -#define SMI_TRESHOLD5
>> >> +
Hi Thomas,
thanks for checking.
On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
> Daniel,
>
> On Thu, 1 Nov 2018, Daniel Vacek wrote:
>
> Please use 'x86/tsc:' as prefix. git log path/to/file usually gives you a
> reasonable hint about prefixes.
Oh, sure th
bailing out unrefined. Usually the next second the readout returns
fast just fine without any issues.
Signed-off-by: Daniel Vacek
---
arch/x86/kernel/tsc.c | 21 +++--
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
index
I do not remember exactly but I guess I used either get_maintainers
script or the email from your commit. I'm sorry for the inconvenience.
> On Fri, Mar 16, 2018 at 03:38:55PM +0100, Daniel Vacek wrote:
>> This reverts commit b92df1de5d289c0b5d653e72414bf0850b8511e0. The commit
On Fri, May 4, 2018 at 6:53 PM, Pavel Tatashin
wrote:
>> I'm wondering, ain't simple enabling of config
>> DEFERRED_STRUCT_PAGE_INIT provide even better speed-up? If that is the
>> case then it seems like this series is not needed at all, right?
>> I am not sure why is this config optional. It loo
On Fri, May 4, 2018 at 4:45 AM, Jia He wrote:
> Ping
>
> Sorry if I am a little bit verbose, but it can speedup the arm64 booting
> time indeed.
I'm wondering, ain't simple enabling of config
DEFERRED_STRUCT_PAGE_INIT provide even better speed-up? If that is the
case then it seems like this serie
On Fri, Apr 6, 2018 at 11:09 AM, Russell King - ARM Linux
wrote:
> On Thu, Apr 05, 2018 at 05:50:54AM -0700, Matthew Wilcox wrote:
>> On Thu, Apr 05, 2018 at 08:44:12PM +0800, Jia He wrote:
>> >
>> >
>> > On 4/5/2018 7:34 PM, Matthew Wilcox Wrote:
>> > > On Thu, Apr 05, 2018 at 01:04:35AM -0700, J
On Mon, Apr 2, 2018 at 8:57 AM, Ard Biesheuvel
wrote:
> On 2 April 2018 at 04:30, Jia He wrote:
>> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>> where possible") optimized the loop in memmap_init_zone(). But there is
>> still some room for improvement. E.g. if pfn and
On Mon, Apr 2, 2018 at 4:30 AM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But there is
> still some room for improvement. E.g. if pfn and pfn+1 are in the same
> memblock region, we can simpl
On Fri, Mar 30, 2018 at 10:15 AM, Jia He wrote:
> This is the preparation for further optimizing in early_pfn_valid
> on arm and arm64.
>
> Signed-off-by: Jia He
> ---
> arch/arm/include/asm/page.h | 3 ++-
> arch/arm/mm/init.c| 23 +++
> arch/arm64/include/asm
On Fri, Mar 30, 2018 at 10:15 AM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But it causes
> possible panic bug. So Daniel Vacek reverted it later.
>
> But as suggest
On Wed, Mar 28, 2018 at 11:26 AM, Jia He wrote:
>
>
> On 3/28/2018 12:52 AM, Daniel Vacek Wrote:
>>
>> On Sat, Mar 24, 2018 at 1:24 PM, Jia He wrote:
>>>
>>> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>>> where pos
On Mon, Mar 26, 2018 at 5:02 AM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But there is
> still some room for improvement. E.g. in early_pfn_valid(), if pfn and
> pfn+1 are in the same memblo
On Mon, Mar 26, 2018 at 5:02 AM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But there is
> still some room for improvement. E.g. if pfn and pfn+1 are in the same
> memblock region, we can simp
On Sat, Mar 24, 2018 at 1:24 PM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But it causes
> possible panic bug. So Daniel Vacek reverted it later.
>
> But membloc
On Wed, Mar 21, 2018 at 1:28 PM, Jia He wrote:
>
> On 3/21/2018 6:14 PM, Daniel Vacek Wrote:
>>
>> On Wed, Mar 21, 2018 at 9:09 AM, Jia He wrote:
>>>
>>> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>>> where possib
On Wed, Mar 21, 2018 at 9:09 AM, Jia He wrote:
> This api is the preparation for further optimizing early_pfn_valid
>
> Signed-off-by: Jia He
> ---
> include/linux/memblock.h | 2 ++
> mm/memblock.c| 12
> 2 files changed, 14 insertions(+)
>
> diff --git a/include/linux
On Wed, Mar 21, 2018 at 9:09 AM, Jia He wrote:
> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> where possible") optimized the loop in memmap_init_zone(). But there is
> still some room for improvement. E.g. if pfn and pfn+1 are in the same
> memblock region, we can simp
Sorry I forgot to Cc: Paul Burton
--nX
On Fri, Mar 16, 2018 at 3:38 PM, Daniel Vacek wrote:
> This reverts commit b92df1de5d289c0b5d653e72414bf0850b8511e0. The commit
> is meant to be a boot init speed up skipping the loop in memmap_init_zone()
> for invalid pfns. But given some
0 1 1f
Fixes: b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns where
possible")
Signed-off-by: Daniel Vacek
Acked-by: Ard Biesheuvel
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Vlastimil Babka
Cc: Mel Gorman
Cc: Pavel Tatashin
Cc: Paul Burton
C
On Thu, Mar 15, 2018 at 3:08 PM, Jia He wrote:
> Hi Daniel
>
>
>
> On 3/14/2018 6:42 AM, Daniel Vacek Wrote:
>>
>> On some architectures (reported on arm64) commit 864b75f9d6b01
>> ("mm/page_alloc: fix memmap_init_zone pageblock alignment")
>> cau
On Thu, Mar 15, 2018 at 4:17 PM, Ard Biesheuvel
wrote:
> On 15 March 2018 at 15:12, Daniel Vacek wrote:
>> On Thu, Mar 15, 2018 at 8:45 AM, Ard Biesheuvel
>> wrote:
>>> On 15 March 2018 at 07:44, Daniel Vacek wrote:
>>>> On Thu, Mar 15, 2018 at 8:36 AM, Ard
On Thu, Mar 15, 2018 at 8:45 AM, Ard Biesheuvel
wrote:
> On 15 March 2018 at 07:44, Daniel Vacek wrote:
>> On Thu, Mar 15, 2018 at 8:36 AM, Ard Biesheuvel
>> wrote:
>>> On 15 March 2018 at 02:23, Daniel Vacek wrote:
>>>> On Wed, Mar 14, 2018 at 8:29 PM, Ar
On Thu, Mar 15, 2018 at 12:50 PM, Michal Hocko wrote:
> On Thu 15-03-18 02:30:41, Daniel Vacek wrote:
>> On Wed, Mar 14, 2018 at 3:17 PM, Michal Hocko wrote:
>> > On Tue 13-03-18 23:42:40, Daniel Vacek wrote:
>> >> On some architectures (reported on arm64) co
On Thu, Mar 15, 2018 at 8:36 AM, Ard Biesheuvel
wrote:
> On 15 March 2018 at 02:23, Daniel Vacek wrote:
>> On Wed, Mar 14, 2018 at 8:29 PM, Ard Biesheuvel
>> wrote:
>>> This reverts commit 864b75f9d6b0100bb24fdd9a20d156e7cda9b5ae.
>>>
>>>
On Thu, Mar 15, 2018 at 7:39 AM, Ard Biesheuvel
wrote:
> On 15 March 2018 at 02:32, Daniel Vacek wrote:
>> On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
>> wrote:
>>> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>>>> On 14 March 2018 at 15:54, Ard
On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
wrote:
> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
>>> On 14 March 2018 at 14:54, Michal Hocko wrote:
On Wed 14-03-18 14:35:12, Ard Biesheuvel wrote:
> On 14 March 2018 at 14:13,
ermediate values following an invalid PFN, we
> may still hit the same VM_BUG_ON() as before.
>
> So instead, let's fix this at the core, and ensure that the BUG
> check doesn't dereference struct page fields of invalid pages.
>
> Fixes: 864b75f9d6b0 ("mm/page_alloc
On Wed, Mar 14, 2018 at 3:17 PM, Michal Hocko wrote:
> On Tue 13-03-18 23:42:40, Daniel Vacek wrote:
>> On some architectures (reported on arm64) commit 864b75f9d6b01
>> ("mm/page_alloc: fix memmap_init_zone pageblock alignment")
>> causes a boot hang. This patch
On Tue, Mar 13, 2018 at 7:34 AM, Naresh Kamboju
wrote:
> On 12 March 2018 at 22:21, Daniel Vacek wrote:
>> On Mon, Mar 12, 2018 at 3:49 PM, Naresh Kamboju
>> wrote:
>>> On 12 March 2018 at 17:56, Sudeep Holla wrote:
>>>> Hi,
>>>>
>>>&g
1520011945.git.ne...@redhat.com
Fixes: 864b75f9d6b01 ("mm/page_alloc: fix memmap_init_zone pageblock alignment")
Signed-off-by: Daniel Vacek
Tested-by: Sudeep Holla
Tested-by: Naresh Kamboju
Cc: Andrew Morton
Cc: Mel Gorman
Cc: Michal Hocko
Cc: Paul Burton
Cc: Pavel Tatashin
Cc:
ey 620 (both arm64). The fix has been proposed and tested but is not
> yet in mainline per https://lkml.org/lkml/2018/3/12/710
I'll send a formal fix today.
> Dan
>
>>
>> --
>>
>> From: Daniel Vacek
>>
>> commit 864b75f9d6b01
[0.00] node 0: [mem 0xfe5d-0xfe5d]
>> [0.00] node 0: [mem 0xfe5e-0xfe62]
>> [0.00] node 0: [mem 0xfe63-0xfeff]
>> [0.00] node 0: [mem 0x00088000-0x0009ff
On Sat, Mar 3, 2018 at 1:40 AM, Andrew Morton wrote:
> On Sat, 3 Mar 2018 01:12:26 +0100 Daniel Vacek wrote:
>
>> Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>> where possible") introduced a bug where move_freepages() triggers a
>>
re minimum of pages is initialized preventing the crash as well.
Fixes: b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns where
possible")
Signed-off-by: Daniel Vacek
Cc: sta...@vger.kernel.org
---
mm/page_alloc.c | 9 +++--
1 file changed, 7 insertions(+),
p. No code changes compared to v2 and
second patch is identical to original v1.
Cc: sta...@vger.kernel.org
Daniel Vacek (2):
mm/memblock: hardcode the max_pfn being -1
mm/page_alloc: fix memmap_init_zone pageblock alignment
mm/memblock.c | 13 ++---
mm/page_alloc.c | 9 +++--
2
This is just a clean up. It aids preventing to handle the special end case
in the next commit.
Signed-off-by: Daniel Vacek
Cc: sta...@vger.kernel.org
---
mm/memblock.c | 13 ++---
mm/page_alloc.c | 2 +-
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/mm/memblock.c b
On Fri, Mar 2, 2018 at 2:01 PM, Michal Hocko wrote:
> On Thu 01-03-18 17:20:04, Daniel Vacek wrote:
>> On Thu, Mar 1, 2018 at 4:27 PM, Michal Hocko wrote:
>> > On Thu 01-03-18 16:09:35, Daniel Vacek wrote:
>> > [...]
>> >> $ grep 7b7ff000 /proc/iom
to pageblock alignment.
To fix this, simply align the skipped pfns in memmap_init_zone()
the same way as in move_freepages_block().
Fixes: b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns where
possible")
Signed-off-by: Daniel Vacek
Cc: sta...@vger.kernel.org
--
On Thu, Mar 1, 2018 at 5:20 PM, Daniel Vacek wrote:
> On Thu, Mar 1, 2018 at 4:27 PM, Michal Hocko wrote:
>> It is still not clear why not to do the alignment in
>> memblock_next_valid_pfn rather than its caller.
>
> As it's the mem init which needs it to be aligne
On Thu, Mar 1, 2018 at 4:27 PM, Michal Hocko wrote:
> On Thu 01-03-18 16:09:35, Daniel Vacek wrote:
>> From registers and stack I digged start_page points to
>> e31d01ed8000 (note that this is
>> page e31d01edffc0 aligned to pageblock) and I can see this in memory
On Thu, Mar 1, 2018 at 4:27 PM, Michal Hocko wrote:
> On Thu 01-03-18 16:09:35, Daniel Vacek wrote:
> [...]
>> $ grep 7b7ff000 /proc/iomem
>> 7b7ff000-7b7f : System RAM
> [...]
>> After commit b92df1de5d28 machine eventually crashes with:
>&g
e31d01ed8000 7b6000 0 0
On Thu, Mar 1, 2018 at 2:10 PM, Michal Hocko wrote:
> On Thu 01-03-18 13:47:45, Daniel Vacek wrote:
>> In move_freepages() a BUG_ON() can be triggered on uninitialized page
>> structures
>> due to pageblock alignment.
valid pfns where
possible")
Signed-off-by: Daniel Vacek
Cc: sta...@vger.kernel.org
---
mm/page_alloc.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index cb416723538f..9edee36e6a74 100644
--- a/mm/page_alloc.c
+++ b/mm/pa
On Tue, Sep 15, 2015 at 3:37 AM, Mike Galbraith
wrote:
> On Mon, 2015-09-14 at 19:11 +0200, Daniel Vacek wrote:
>> On Mon, Sep 14, 2015 at 1:42 PM, Thomas Gleixner wrote:
>> > I'm not going to support 4.2. We switched to odd numbers due to 4.1
>> > being a LTS k
On Mon, Sep 14, 2015 at 1:42 PM, Thomas Gleixner wrote:
> I'm not going to support 4.2. We switched to odd numbers due to 4.1
> being a LTS kernel.
That's odd.
--nX
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
M
On Wed, Apr 3, 2013 at 12:28 PM, Matt Fleming wrote:
>
> On 30/03/13 10:04, Daniel Vacek wrote:
> >
> > Resending patch. It got lost somewhere. Thanks for pushing Ben.
>
> I applied this by hand. Your patch appears to be whitespace damaged.
You're right. Sorry f
Ben.
>From 53864fe932aa87be62f1c70944c386cff9bb9130 Mon Sep 17 00:00:00 2001
From: Daniel Vacek
Date: Thu, 18 Oct 2012 22:06:26 +0200
Subject: [PATCH] efi: fix typo in Makefile
Fix a little typo.
Signed-off-by: Daniel Vacek
Acked-by: Matthew Garrett
---
arch/x86/boot/compressed/Makefile |2 +-
1 file changed, 1 i
On Wed, Dec 5, 2012 at 12:02 PM, Daniel Vacek wrote:
> On Tue, Dec 4, 2012 at 4:54 PM, Tejun Heo wrote:
>> @@ -5190,7 +5188,7 @@ static void
>> megasas_aen_polling(struct work_struct *work)
>> {
>> struct megasas_aen_event *ev =
>> -
On Tue, Dec 4, 2012 at 4:54 PM, Tejun Heo wrote:
> @@ -5190,7 +5188,7 @@ static void
> megasas_aen_polling(struct work_struct *work)
> {
> struct megasas_aen_event *ev =
> - container_of(work, struct megasas_aen_event, hotplug_work);
> + container_of(work, str
On Wed, Oct 24, 2012 at 7:52 PM, Greg KH wrote:
> On Thu, Oct 18, 2012 at 10:32:50PM +0200, Daniel Vacek wrote:
>> On Thu, Oct 18, 2012 at 8:28 PM, Matthew Garrett wrote:
>> > On Thu, Oct 18, 2012 at 08:18:51PM +0200, Daniel Vacek wrote:
>> >
>> >> s/
On Thu, Oct 18, 2012 at 8:28 PM, Matthew Garrett wrote:
> On Thu, Oct 18, 2012 at 08:18:51PM +0200, Daniel Vacek wrote:
>
>> s/CLFAGS/CFLAGS/
>>
>> should go to stable too?
>
> Crap. Yes. Feel free to send that.
--nX
0001-efi-fix-typo-in-Makefile.patch
Description: Binary data
On Fri, Jul 27, 2012 at 12:00 AM, Matthew Garrett wrote:
> We can't assume the presence of the red zone while we're still in a boot
> services environment, so we should build with -fno-red-zone to avoid
> problems. Change the size of wchar at the same time to make string handling
> simpler.
>
> Si
59 matches
Mail list logo
