From: Oleksandr <olekstysh@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Mirela Simonovic <mirela.simonovic@aggios.com>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH v2 1/2] xen/arm: link: Link proc_info_list in .data instead of .init.data
Date: Fri, 7 Dec 2018 15:51:32 +0200 [thread overview]
Message-ID: <e6e4ceb3-0d13-a33b-4950-93f445b282bb@gmail.com> (raw)
In-Reply-To: <67c109bd-17a1-baea-40af-53c60d520c6b@arm.com>
On 07.12.18 12:34, Julien Grall wrote:
> Hi Oleksandr,
Hi Julien
>
> Please configure your client to quote with > rather than indentation.
> Below is an example how it can get messy in just 3 answers, I let you
> imagine with longer thread :).
>
> This is a general issue with gmail web-interface that quote using
> tabulation. It would be best if you use an external mail client (e.g
> thunderbird, mute...).
Have already configured, sorry for the inconvenience.
>
> On 07/12/2018 10:32, Oleksandr Tyshchenko wrote:
>>
>>
>> On Fri, Dec 7, 2018 at 12:05 PM Julien Grall <julien.grall@arm.com
>> <mailto:julien.grall@arm.com>> wrote:
>>
>> Hi Oleksandr,
>>
>> Hi Julien
>>
>>
>> On 07/12/2018 09:45, Oleksandr Tyshchenko wrote:
>> > From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com
>> <mailto:oleksandr_tyshchenko@epam.com>>
>> >
>> > To be able to use it for the hot-plugged CPUs as well.
>>
>> You need to explain in the commit message why you rename
>> .init.proc.info
>> <http://init.proc.info>.
>>
>> ok
>>
>>
>> >
>> > Signed-off-by: Oleksandr Tyshchenko
>> <oleksandr_tyshchenko@epam.com
>> <mailto:oleksandr_tyshchenko@epam.com>>
>> >
>> > ---
>> > Changes in v2:
>> > - Fix typoes
>> > - Rename ".init.proc.info <http://init.proc.info>" to
>> ".data.proc.info <http://data.proc.info>"
>> > ---
>> > xen/arch/arm/arm32/proc-v7.S | 6 +++---
>> > xen/arch/arm/xen.lds.S | 10 ++++++----
>> > 2 files changed, 9 insertions(+), 7 deletions(-)
>> >
>> > diff --git a/xen/arch/arm/arm32/proc-v7.S
>> b/xen/arch/arm/arm32/proc-v7.S
>> > index 80a250d..a0c0c9e 100644
>> > --- a/xen/arch/arm/arm32/proc-v7.S
>> > +++ b/xen/arch/arm/arm32/proc-v7.S
>> > @@ -30,7 +30,7 @@ brahma15mp_init:
>> > mcr CP32(r0, ACTLR)
>> > mov pc, lr
>> >
>> > - .section ".init.proc.info <http://init.proc.info>",
>> #alloc,
>> #execinstr
>> > + .section ".data.proc.info <http://data.proc.info>",
>> #alloc,
>> #execinstr
>>
>> NIT: .proc.info <http://proc.info> would be sufficient. This
>> would avoid to
>> rename again the
>> section if we decide to move it in a separate section.
>>
>> ok
>>
>>
>> > .type __v7_ca15mp_proc_info, #object
>> > __v7_ca15mp_proc_info:
>> > .long 0x410FC0F0 /* Cortex-A15 */
>> > @@ -39,7 +39,7 @@ __v7_ca15mp_proc_info:
>> > .long caxx_processor
>> > .size __v7_ca15mp_proc_info, . - __v7_ca15mp_proc_info
>> >
>> > - .section ".init.proc.info <http://init.proc.info>",
>> #alloc,
>> #execinstr
>> > + .section ".data.proc.info <http://data.proc.info>",
>> #alloc,
>> #execinstr
>> > .type __v7_ca7mp_proc_info, #object
>> > __v7_ca7mp_proc_info:
>> > .long 0x410FC070 /* Cortex-A7 */
>> > @@ -48,7 +48,7 @@ __v7_ca7mp_proc_info:
>> > .long caxx_processor
>> > .size __v7_ca7mp_proc_info, . - __v7_ca7mp_proc_info
>> >
>> > - .section ".init.proc.info <http://init.proc.info>",
>> #alloc,
>> #execinstr
>> > + .section ".data.proc.info <http://data.proc.info>",
>> #alloc,
>> #execinstr
>> > .type __v7_brahma15mp_proc_info, #object
>> > __v7_brahma15mp_proc_info:
>> > .long 0x420F00F0 /* Broadcom Brahma-B15 */
>> > diff --git a/xen/arch/arm/xen.lds.S b/xen/arch/arm/xen.lds.S
>> > index 245a0e0..624da9b 100644
>> > --- a/xen/arch/arm/xen.lds.S
>> > +++ b/xen/arch/arm/xen.lds.S
>> > @@ -88,6 +88,12 @@ SECTIONS
>> > . = ALIGN(PAGE_SIZE);
>> > *(.data.page_aligned)
>> > *(.data)
>> > +
>> > + . = ALIGN(POINTER_ALIGN);
>> > + __proc_info_start = .;
>> > + *(.data.proc.info <http://data.proc.info>)
>> > + __proc_info_end = .;
>>
>> Sorry I haven't noticed it in the previous version. proc.info
>> <http://proc.info> should never
>> modified, right? So it should be in rodata in that case.
>>
>> agree, will link it in rodata.
>>
>> May I resend just this patch after address your comments?
>
> Yes please. I will commit the other soon.
Done.
https://lists.xenproject.org/archives/html/xen-devel/2018-12/msg00777.html
>
> Cheers,
>
--
Regards,
Oleksandr Tyshchenko
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-07 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 9:45 [PATCH v2 0/2] CPU hotplug fixes for ARM32 Oleksandr Tyshchenko
2018-12-07 9:45 ` [PATCH v2 1/2] xen/arm: link: Link proc_info_list in .data instead of .init.data Oleksandr Tyshchenko
2018-12-07 10:05 ` Julien Grall
2018-12-07 10:32 ` Oleksandr Tyshchenko
2018-12-07 10:34 ` Julien Grall
2018-12-07 13:51 ` Oleksandr [this message]
2018-12-07 9:45 ` [PATCH v2 2/2] xen/arm32: Remove __init prefixes from funcs that are used within CPU up flow Oleksandr Tyshchenko
2018-12-07 10:02 ` [PATCH v2 0/2] CPU hotplug fixes for ARM32 Julien Grall
2018-12-07 12:21 ` Oleksandr
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=e6e4ceb3-0d13-a33b-4950-93f445b282bb@gmail.com \
--to=olekstysh@gmail.com \
--cc=julien.grall@arm.com \
--cc=mirela.simonovic@aggios.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.