From: ebiederm@xmission.com (Eric W. Biederman)
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: fenghua.yu@intel.com, tony.luck@intel.com,
linux-ia64@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Dave Young <dyoung@redhat.com>,
vgoyal@redhat.com
Subject: Re: [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Fri, 02 Dec 2016 13:22:39 -0600 [thread overview]
Message-ID: <87mvge16gw.fsf@xmission.com> (raw)
In-Reply-To: <fe3784de-a68b-5d6e-a9ab-f77a7da781a8@linux.vnet.ibm.com> (Hari Bathini's message of "Fri, 2 Dec 2016 16:56:48 +0530")
Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
> Hi Dave,
>
>
> Thanks for the review.
>
>
> On Thursday 01 December 2016 10:26 AM, Dave Young wrote:
>> Hi Hari
>>
>> Personally I like V1 more, but split the patch 2 is easier for ia64
>> people to reivew. I did basic x86 testing, it runs ok.
>>
>> On 11/25/16 at 05:24pm, Hari Bathini wrote:
>>> Get rid of multiple definitions of append_elf_note() & final_note()
>>> functions. Reuse these functions compiled under CONFIG_CRASH_CORE.
>>>
>>> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
>>> ---
>>> arch/ia64/kernel/crash.c | 22 ----------------------
>>> include/linux/crash_core.h | 4 ++++
>>> kernel/crash_core.c | 6 +++---
>>> kernel/kexec_core.c | 28 ----------------------------
>>> 4 files changed, 7 insertions(+), 53 deletions(-)
>>>
>>> diff --git a/arch/ia64/kernel/crash.c b/arch/ia64/kernel/crash.c
>>> index 2955f35..75859a0 100644
>>> --- a/arch/ia64/kernel/crash.c
>>> +++ b/arch/ia64/kernel/crash.c
>>> @@ -27,28 +27,6 @@ static int kdump_freeze_monarch;
>>> static int kdump_on_init = 1;
>>> static int kdump_on_fatal_mca = 1;
>>> -static inline Elf64_Word
>>> -*append_elf_note(Elf64_Word *buf, char *name, unsigned type, void *data,
>>> - size_t data_len)
>>> -{
>>> - struct elf_note *note = (struct elf_note *)buf;
>>> - note->n_namesz = strlen(name) + 1;
>>> - note->n_descsz = data_len;
>>> - note->n_type = type;
>>> - buf += (sizeof(*note) + 3)/4;
>>> - memcpy(buf, name, note->n_namesz);
>>> - buf += (note->n_namesz + 3)/4;
>>> - memcpy(buf, data, data_len);
>>> - buf += (data_len + 3)/4;
>>> - return buf;
>>> -}
>>> -
>>> -static void
>>> -final_note(void *buf)
>>> -{
>>> - memset(buf, 0, sizeof(struct elf_note));
>>> -}
>>> -
>> The above IA64 version looks better than the functions in kexec_core.c
>> about the Elf64_Word type usage and the simpler final_note function.
>
> Hmmm.. Is void* better over Elf64_Word* to be agnostic of Elf32 or
> Elf64 type?
Both Elf64_Word and Elf32_Word result in a u32. So I expect the right
solution is to add a definition of Elf_Word to include/linux/elf.h
and to make the buffer "Elf_Word *buf".
That way we preserve the alignment knowledge, while making the code
depend on 32bit or 64bit.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: Dave Young <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, fenghua.yu@intel.com,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
vgoyal@redhat.com
Subject: Re: [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Fri, 02 Dec 2016 19:22:39 +0000 [thread overview]
Message-ID: <87mvge16gw.fsf@xmission.com> (raw)
In-Reply-To: <fe3784de-a68b-5d6e-a9ab-f77a7da781a8@linux.vnet.ibm.com> (Hari Bathini's message of "Fri, 2 Dec 2016 16:56:48 +0530")
Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
> Hi Dave,
>
>
> Thanks for the review.
>
>
> On Thursday 01 December 2016 10:26 AM, Dave Young wrote:
>> Hi Hari
>>
>> Personally I like V1 more, but split the patch 2 is easier for ia64
>> people to reivew. I did basic x86 testing, it runs ok.
>>
>> On 11/25/16 at 05:24pm, Hari Bathini wrote:
>>> Get rid of multiple definitions of append_elf_note() & final_note()
>>> functions. Reuse these functions compiled under CONFIG_CRASH_CORE.
>>>
>>> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
>>> ---
>>> arch/ia64/kernel/crash.c | 22 ----------------------
>>> include/linux/crash_core.h | 4 ++++
>>> kernel/crash_core.c | 6 +++---
>>> kernel/kexec_core.c | 28 ----------------------------
>>> 4 files changed, 7 insertions(+), 53 deletions(-)
>>>
>>> diff --git a/arch/ia64/kernel/crash.c b/arch/ia64/kernel/crash.c
>>> index 2955f35..75859a0 100644
>>> --- a/arch/ia64/kernel/crash.c
>>> +++ b/arch/ia64/kernel/crash.c
>>> @@ -27,28 +27,6 @@ static int kdump_freeze_monarch;
>>> static int kdump_on_init = 1;
>>> static int kdump_on_fatal_mca = 1;
>>> -static inline Elf64_Word
>>> -*append_elf_note(Elf64_Word *buf, char *name, unsigned type, void *data,
>>> - size_t data_len)
>>> -{
>>> - struct elf_note *note = (struct elf_note *)buf;
>>> - note->n_namesz = strlen(name) + 1;
>>> - note->n_descsz = data_len;
>>> - note->n_type = type;
>>> - buf += (sizeof(*note) + 3)/4;
>>> - memcpy(buf, name, note->n_namesz);
>>> - buf += (note->n_namesz + 3)/4;
>>> - memcpy(buf, data, data_len);
>>> - buf += (data_len + 3)/4;
>>> - return buf;
>>> -}
>>> -
>>> -static void
>>> -final_note(void *buf)
>>> -{
>>> - memset(buf, 0, sizeof(struct elf_note));
>>> -}
>>> -
>> The above IA64 version looks better than the functions in kexec_core.c
>> about the Elf64_Word type usage and the simpler final_note function.
>
> Hmmm.. Is void* better over Elf64_Word* to be agnostic of Elf32 or
> Elf64 type?
Both Elf64_Word and Elf32_Word result in a u32. So I expect the right
solution is to add a definition of Elf_Word to include/linux/elf.h
and to make the buffer "Elf_Word *buf".
That way we preserve the alignment knowledge, while making the code
depend on 32bit or 64bit.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: Dave Young <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, fenghua.yu@intel.com,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
kexec@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
vgoyal@redhat.com
Subject: Re: [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions
Date: Fri, 02 Dec 2016 13:22:39 -0600 [thread overview]
Message-ID: <87mvge16gw.fsf@xmission.com> (raw)
In-Reply-To: <fe3784de-a68b-5d6e-a9ab-f77a7da781a8@linux.vnet.ibm.com> (Hari Bathini's message of "Fri, 2 Dec 2016 16:56:48 +0530")
Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
> Hi Dave,
>
>
> Thanks for the review.
>
>
> On Thursday 01 December 2016 10:26 AM, Dave Young wrote:
>> Hi Hari
>>
>> Personally I like V1 more, but split the patch 2 is easier for ia64
>> people to reivew. I did basic x86 testing, it runs ok.
>>
>> On 11/25/16 at 05:24pm, Hari Bathini wrote:
>>> Get rid of multiple definitions of append_elf_note() & final_note()
>>> functions. Reuse these functions compiled under CONFIG_CRASH_CORE.
>>>
>>> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
>>> ---
>>> arch/ia64/kernel/crash.c | 22 ----------------------
>>> include/linux/crash_core.h | 4 ++++
>>> kernel/crash_core.c | 6 +++---
>>> kernel/kexec_core.c | 28 ----------------------------
>>> 4 files changed, 7 insertions(+), 53 deletions(-)
>>>
>>> diff --git a/arch/ia64/kernel/crash.c b/arch/ia64/kernel/crash.c
>>> index 2955f35..75859a0 100644
>>> --- a/arch/ia64/kernel/crash.c
>>> +++ b/arch/ia64/kernel/crash.c
>>> @@ -27,28 +27,6 @@ static int kdump_freeze_monarch;
>>> static int kdump_on_init = 1;
>>> static int kdump_on_fatal_mca = 1;
>>> -static inline Elf64_Word
>>> -*append_elf_note(Elf64_Word *buf, char *name, unsigned type, void *data,
>>> - size_t data_len)
>>> -{
>>> - struct elf_note *note = (struct elf_note *)buf;
>>> - note->n_namesz = strlen(name) + 1;
>>> - note->n_descsz = data_len;
>>> - note->n_type = type;
>>> - buf += (sizeof(*note) + 3)/4;
>>> - memcpy(buf, name, note->n_namesz);
>>> - buf += (note->n_namesz + 3)/4;
>>> - memcpy(buf, data, data_len);
>>> - buf += (data_len + 3)/4;
>>> - return buf;
>>> -}
>>> -
>>> -static void
>>> -final_note(void *buf)
>>> -{
>>> - memset(buf, 0, sizeof(struct elf_note));
>>> -}
>>> -
>> The above IA64 version looks better than the functions in kexec_core.c
>> about the Elf64_Word type usage and the simpler final_note function.
>
> Hmmm.. Is void* better over Elf64_Word* to be agnostic of Elf32 or
> Elf64 type?
Both Elf64_Word and Elf32_Word result in a u32. So I expect the right
solution is to add a definition of Elf_Word to include/linux/elf.h
and to make the buffer "Elf_Word *buf".
That way we preserve the alignment knowledge, while making the code
depend on 32bit or 64bit.
Eric
next prev parent reply other threads:[~2016-12-02 19:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 11:53 [PATCH v2 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2016-11-25 11:53 ` [PATCH v2 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for Hari Bathini
2016-11-25 11:53 ` [PATCH v2 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2016-11-25 11:53 ` [PATCH v2 1/5] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:53 ` Hari Bathini
2016-11-25 11:54 ` [PATCH v2 2/5] ia64: reuse append_elf_note() and final_note() functions Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-12-01 4:56 ` Dave Young
2016-12-01 4:56 ` Dave Young
2016-12-01 4:56 ` Dave Young
2016-12-02 11:26 ` Hari Bathini
2016-12-02 11:38 ` Hari Bathini
2016-12-02 11:26 ` Hari Bathini
2016-12-02 19:22 ` Eric W. Biederman [this message]
2016-12-02 19:22 ` Eric W. Biederman
2016-12-02 19:22 ` Eric W. Biederman
2016-12-16 6:37 ` Hari Bathini
2016-12-16 6:49 ` Hari Bathini
2016-12-16 6:37 ` Hari Bathini
2016-11-25 11:54 ` [PATCH v2 3/5] powerpc/fadump: remove dependency with CONFIG_KEXEC Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` [PATCH v2 4/5] powerpc/fadump: reuse crashkernel parameter for fadump memory reservation Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` [PATCH v2 5/5] powerpc/fadump: update documentation about crashkernel parameter reuse Hari Bathini
2016-11-25 11:54 ` Hari Bathini
2016-11-25 11:54 ` Hari Bathini
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=87mvge16gw.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=dyoung@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.