On Fri, Feb 15, 2019 at 12:14:32PM +0100, Igor Mammedov wrote:
>On Thu, 14 Feb 2019 20:53:31 +
>Wei Yang wrote:
>
>> On Thu, Feb 14, 2019 at 12:25:27PM +0100, Igor Mammedov wrote:
>> >On Thu, 14 Feb 2019 08:52:25 +0800
>> >Wei Yang wrote:
>> >
>> >> Currently we do device realization like bel
On Thu, 14 Feb 2019 20:53:31 +
Wei Yang wrote:
> On Thu, Feb 14, 2019 at 12:25:27PM +0100, Igor Mammedov wrote:
> >On Thu, 14 Feb 2019 08:52:25 +0800
> >Wei Yang wrote:
> >
> >> Currently we do device realization like below:
> >>
> >>hotplug_handler_pre_plug()
> >>dc->realize()
> >>
On Thu, Feb 14, 2019 at 12:25:27PM +0100, Igor Mammedov wrote:
>On Thu, 14 Feb 2019 08:52:25 +0800
>Wei Yang wrote:
>
>> Currently we do device realization like below:
>>
>>hotplug_handler_pre_plug()
>>dc->realize()
>>hotplug_handler_plug()
>>
>> Before we do device realization and p
On Thu, 14 Feb 2019 08:52:25 +0800
Wei Yang wrote:
> Currently we do device realization like below:
>
>hotplug_handler_pre_plug()
>dc->realize()
>hotplug_handler_plug()
>
> Before we do device realization and plug, we would allocate necessary
> resources and check the capacity.
'cap
Currently we do device realization like below:
hotplug_handler_pre_plug()
dc->realize()
hotplug_handler_plug()
Before we do device realization and plug, we would allocate necessary
resources and check the capacity.
While we leave acpi_memory_hotplug capacity check in the last step. This