[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1 3/3] xen/common: move device initialization code to common code


  • To: oleksii.kurochko@xxxxxxxxx
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Mon, 23 Sep 2024 09:20:36 +0200
  • Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
  • Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 23 Sep 2024 07:20:43 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 16.09.2024 17:51, oleksii.kurochko@xxxxxxxxx wrote:
> On Fri, 2024-09-13 at 19:45 +0200, Jan Beulich wrote:
>> On 13.09.2024 16:35, oleksii.kurochko@xxxxxxxxx wrote:
>>> On Thu, 2024-09-12 at 17:28 +0200, Jan Beulich wrote:
>>>> On 11.09.2024 12:04, Oleksii Kurochko wrote:
>>>>> --- a/xen/common/Makefile
>>>>> +++ b/xen/common/Makefile
>>>>> @@ -6,6 +6,7 @@ obj-$(CONFIG_HYPFS_CONFIG) += config_data.o
>>>>>  obj-$(CONFIG_CORE_PARKING) += core_parking.o
>>>>>  obj-y += cpu.o
>>>>>  obj-$(CONFIG_DEBUG_TRACE) += debugtrace.o
>>>>> +obj-$(call or,$(CONFIG_HAS_DEVICE_TREE),$(CONFIG_HAS_ACPI)) +=
>>>>> device.o
>>>>
>>>> I can't spot any HAS_ACPI in the tree. And if this was switched
>>>> to
>>>> CONFIG_ACPI
>>>> I'd further ask why the file needs building on x86.
>>> Oh, there is no need for building this on x86. With what you
>>> suggested
>>> here ...
>>>
>>>>
>>>> Also I think I'd prefer to avoid the of the "or" macro here:
>>>>
>>>> obj-$(CONFIG_ACPI) += device.o
>>>> obj-$(CONFIG_HAS_DEVICE_TREE) += device.o
>>> ... IIUC it will fix the issue with building this file for x86 as
>>> CONFIG_ACPI depends on (ARM_64 && ARM_EFI).
>>
>> Except that "depends on" is itself Arm-only, so won't affect x86.
>> Or else x86 would end up without ACPI support, which would mean
>> full breakage on about every system.
> There is another CONFIG_ACPI in xen/drivers/acpi which is equal to 'y'
> for x86 so it seems to me that it is needed another config (
> GENERIC_DEVICE_INIT ? ) which will be disabled for x86 by default so
> device.o won't be compiled for x86.
> 
> Have I overlooked something or better option exist? Probably it would
> be better to use "and" macro?

I'm afraid I don't understand your response. There are two seemingly
separate ACPI in distinct Kconfig files, yes. They combine when both are
visible to kconfig (as is the case for Arm64). Can you try to re-express
your question with this aspect in mind?

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.