From: boris.ostrovsky@oracle.com (Boris Ostrovsky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] xen/arm: Enable cpu_hotplug.c
Date: Thu, 22 Oct 2015 12:15:06 -0400 [thread overview]
Message-ID: <56290B8A.8040501@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510221713160.15801@kaball.uk.xensource.com>
On 10/22/2015 12:13 PM, Stefano Stabellini wrote:
> On Wed, 21 Oct 2015, Stefano Stabellini wrote:
>> On Wed, 21 Oct 2015, Boris Ostrovsky wrote:
>>> On 10/21/2015 09:00 AM, Stefano Stabellini wrote:
>>>>> diff --git a/arch/x86/include/asm/xen/hypervisor.h
>>>>> b/arch/x86/include/asm/xen/hypervisor.h
>>>>> index d866959..8b2d4be 100644
>>>>> --- a/arch/x86/include/asm/xen/hypervisor.h
>>>>> +++ b/arch/x86/include/asm/xen/hypervisor.h
>>>>> @@ -57,4 +57,9 @@ static inline bool xen_x2apic_para_available(void)
>>>>> }
>>>>> #endif
>>>>> +#ifdef CONFIG_HOTPLUG_CPU
>>>>> +void xen_arch_register_cpu(int num);
>>>>> +void xen_arch_unregister_cpu(int num);
>>>>> +#endif
>>> Why not inline them here, just like you did for ARM?
>> I don't think is good practice to define static inline functions under
>> arch/something, then use them under drivers/something_else. It is
>> tolerable if the static inline functions are empty and the driver in
>> question cannot be compiled as module, like in this case for the arm.
>>
>> In addition the x86 implementation calls arch_(un)register_cpu, which
>> requires #include <asm/cpu.h>, which doesn't compile if added to
>> arch/x86/include/asm/xen/hypervisor.h.
> Boris, does this explanation satisfy you?
> Do you want me to change anything?
Sorry, I forgot to respond!
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
WARNING: multiple messages have this Message-ID (diff)
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Julien Grall <julien.grall@citrix.com>,
xen-devel@lists.xensource.com, david.vrabel@citrix.com,
linux-arm-kernel@lists.infradead.org, konrad.wilk@oracle.com
Subject: Re: [PATCH v4 1/3] xen/arm: Enable cpu_hotplug.c
Date: Thu, 22 Oct 2015 12:15:06 -0400 [thread overview]
Message-ID: <56290B8A.8040501@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510221713160.15801@kaball.uk.xensource.com>
On 10/22/2015 12:13 PM, Stefano Stabellini wrote:
> On Wed, 21 Oct 2015, Stefano Stabellini wrote:
>> On Wed, 21 Oct 2015, Boris Ostrovsky wrote:
>>> On 10/21/2015 09:00 AM, Stefano Stabellini wrote:
>>>>> diff --git a/arch/x86/include/asm/xen/hypervisor.h
>>>>> b/arch/x86/include/asm/xen/hypervisor.h
>>>>> index d866959..8b2d4be 100644
>>>>> --- a/arch/x86/include/asm/xen/hypervisor.h
>>>>> +++ b/arch/x86/include/asm/xen/hypervisor.h
>>>>> @@ -57,4 +57,9 @@ static inline bool xen_x2apic_para_available(void)
>>>>> }
>>>>> #endif
>>>>> +#ifdef CONFIG_HOTPLUG_CPU
>>>>> +void xen_arch_register_cpu(int num);
>>>>> +void xen_arch_unregister_cpu(int num);
>>>>> +#endif
>>> Why not inline them here, just like you did for ARM?
>> I don't think is good practice to define static inline functions under
>> arch/something, then use them under drivers/something_else. It is
>> tolerable if the static inline functions are empty and the driver in
>> question cannot be compiled as module, like in this case for the arm.
>>
>> In addition the x86 implementation calls arch_(un)register_cpu, which
>> requires #include <asm/cpu.h>, which doesn't compile if added to
>> arch/x86/include/asm/xen/hypervisor.h.
> Boris, does this explanation satisfy you?
> Do you want me to change anything?
Sorry, I forgot to respond!
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2015-10-22 16:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 11:52 [PATCH v4] xen,arm: enable cpu_hotplug Stefano Stabellini
2015-10-21 11:52 ` Stefano Stabellini
2015-10-21 11:53 ` [PATCH v4 1/3] xen/arm: Enable cpu_hotplug.c Stefano Stabellini
2015-10-21 11:53 ` Stefano Stabellini
2015-10-21 13:00 ` Stefano Stabellini
2015-10-21 13:00 ` Stefano Stabellini
2015-10-21 13:19 ` Boris Ostrovsky
2015-10-21 13:19 ` Boris Ostrovsky
2015-10-21 15:36 ` Stefano Stabellini
2015-10-21 15:36 ` Stefano Stabellini
2015-10-22 16:13 ` Stefano Stabellini
2015-10-22 16:13 ` Stefano Stabellini
2015-10-22 16:15 ` Boris Ostrovsky [this message]
2015-10-22 16:15 ` Boris Ostrovsky
2015-10-22 16:22 ` Stefano Stabellini
2015-10-22 16:22 ` Stefano Stabellini
2015-10-21 11:53 ` [PATCH v4 2/3] xen, cpu_hotplug: call device_offline instead of cpu_down Stefano Stabellini
2015-10-21 11:53 ` Stefano Stabellini
2015-10-21 12:56 ` Boris Ostrovsky
2015-10-21 12:56 ` Boris Ostrovsky
2015-10-21 11:53 ` [PATCH v4 3/3] xen/arm: don't try to re-register vcpu_info on cpu_hotplug Stefano Stabellini
2015-10-21 11:53 ` Stefano Stabellini
2015-10-21 11:55 ` [Xen-devel] " Julien Grall
2015-10-21 11:55 ` Julien Grall
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=56290B8A.8040501@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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.