From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>,
Jeremiah Mahler <jmmahler@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Remove excess calculations for heap_end_ptr
Date: Fri, 26 Dec 2014 09:04:51 -0800 [thread overview]
Message-ID: <60579BEB-2AD0-4A4E-BFC8-FE0BDB688DC7@zytor.com> (raw)
In-Reply-To: <CANCZXo4LbSrUU_=LuXmrJ3=aC6cvtDD77JVa6Hhe1y5GTNuK5g@mail.gmail.com>
Yes, the -512 is not related to STACK_SIZE, so this patch is wrong. NAK.
On December 26, 2014 9:03:38 AM PST, Alexander Kuleshov <kuleshovmail@gmail.com> wrote:
>Yes, you're right,
>
>At first i thought that it is just typo, and right after that i
>thought about this case when somebody will change STACK_SIZE
>
>2014-12-26 20:35 GMT+06:00 Jeremiah Mahler <jmmahler@gmail.com>:
>> Alexander,
>>
>> On Fri, Dec 26, 2014 at 06:22:42PM +0600, Alexander Kuleshov wrote:
>>> heap_end_ptr default value defined as _end+STACK_SZE-512, but
>> STACK_SIZE
>>
>>> STACK_SIZE is already 512.
>>>
>>> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
>>> ---
>>> arch/x86/boot/header.S | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
>>> index 16ef025..c69b870 100644
>>> --- a/arch/x86/boot/header.S
>>> +++ b/arch/x86/boot/header.S
>>> @@ -342,7 +342,7 @@ ramdisk_size: .long 0 # its
>size in bytes
>>> bootsect_kludge:
>>> .long 0 # obsolete
>>>
>>> -heap_end_ptr: .word _end+STACK_SIZE-512
>>> +heap_end_ptr: .word _end
>>> # (Header version 0x0201 or
>later)
>>> # space from here (exclusive)
>down to
>>> # end of setup code can be
>used by setup
>>
>> So right now STACK_SIZE happens to be 512 so STACK_SIZE-512 is zero.
>> What happens if someone changes the size of STACK_SIZE?
>>
>> This change doesn't fix any problem right now and creates potential
>> problems in the future.
>>
>>> --
>>> 2.2.1.201.gbbcefff
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at http://www.tux.org/lkml/
>>
>> --
>> - Jeremiah Mahler
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
prev parent reply other threads:[~2014-12-26 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 12:22 Alexander Kuleshov
2014-12-26 14:35 ` Jeremiah Mahler
2014-12-26 17:03 ` Alexander Kuleshov
2014-12-26 17:04 ` H. Peter Anvin [this message]
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=60579BEB-2AD0-4A4E-BFC8-FE0BDB688DC7@zytor.com \
--to=hpa@zytor.com \
--cc=jmmahler@gmail.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®