Hi Eric,
On 22/04/2020 14:04, Eric W. Biederman wrote:
> James Morse writes:
>> On 15/04/2020 21:29, Eric W. Biederman wrote:
>>> James Morse writes:
arm64 recently queued support for memory hotremove, which led to some
new corner cases for kexec.
If the kexec segments are
James Morse writes:
> Hi Eric,
>
> On 15/04/2020 21:29, Eric W. Biederman wrote:
>> James Morse writes:
>>
>>> Hello!
>>>
>>> arm64 recently queued support for memory hotremove, which led to some
>>> new corner cases for kexec.
>>>
>>> If the kexec segments are loaded for a removable region,
Hi Eric,
On 15/04/2020 21:29, Eric W. Biederman wrote:
> James Morse writes:
>
>> Hello!
>>
>> arm64 recently queued support for memory hotremove, which led to some
>> new corner cases for kexec.
>>
>> If the kexec segments are loaded for a removable region, that region may
>> be removed before
James Morse writes:
> Hello!
>
> arm64 recently queued support for memory hotremove, which led to some
> new corner cases for kexec.
>
> If the kexec segments are loaded for a removable region, that region may
> be removed before kexec actually occurs. This causes the first kernel to
> lockup
Hi Dave,
On 31/03/2020 04:46, Dave Young wrote:
> I agreed that file load is still not widely used, but in the long run
> we should not maintain both of them all the future time. Especially
> when some kernel-userspace interfaces need to be introduced, file load
> will have the natural
Hi James,
On 03/30/20 at 06:17pm, James Morse wrote:
> Hi Baoquan,
>
> On 3/30/20 2:55 PM, Baoquan He wrote:
> > On 03/26/20 at 06:07pm, James Morse wrote:
> >> arm64 recently queued support for memory hotremove, which led to some
> >> new corner cases for kexec.
> >>
> >> If the kexec segments
Hi James,
On 03/26/20 at 06:07pm, James Morse wrote:
> Hello!
>
> arm64 recently queued support for memory hotremove, which led to some
> new corner cases for kexec.
>
> If the kexec segments are loaded for a removable region, that region may
> be removed before kexec actually occurs. This
Hi Baoquan,
On 3/30/20 2:55 PM, Baoquan He wrote:
> On 03/26/20 at 06:07pm, James Morse wrote:
>> arm64 recently queued support for memory hotremove, which led to some
>> new corner cases for kexec.
>>
>> If the kexec segments are loaded for a removable region, that region may
>> be removed
Hi James,
On 03/26/20 at 06:07pm, James Morse wrote:
> Hello!
>
> arm64 recently queued support for memory hotremove, which led to some
> new corner cases for kexec.
>
> If the kexec segments are loaded for a removable region, that region may
> be removed before kexec actually occurs. This
On 27.03.20 16:42, James Morse wrote:
> Hi David,
>
> On 3/27/20 9:27 AM, David Hildenbrand wrote:
>> On 26.03.20 19:07, James Morse wrote:
>>> arm64 recently queued support for memory hotremove, which led to some
>>> new corner cases for kexec.
>>>
>>> If the kexec segments are loaded for a
Hi David,
On 3/27/20 9:27 AM, David Hildenbrand wrote:
> On 26.03.20 19:07, James Morse wrote:
>> arm64 recently queued support for memory hotremove, which led to some
>> new corner cases for kexec.
>>
>> If the kexec segments are loaded for a removable region, that region may
>> be removed
Hi Baoquan,
On 3/27/20 2:11 AM, Baoquan He wrote:
> On 03/26/20 at 06:07pm, James Morse wrote:
>> arm64 recently queued support for memory hotremove, which led to some
>> new corner cases for kexec.
>>
>> If the kexec segments are loaded for a removable region, that region may
>> be removed
On 26.03.20 19:07, James Morse wrote:
> Hello!
>
> arm64 recently queued support for memory hotremove, which led to some
> new corner cases for kexec.
>
> If the kexec segments are loaded for a removable region, that region may
> be removed before kexec actually occurs. This causes the first
On 03/26/20 at 06:07pm, James Morse wrote:
> Hello!
>
> arm64 recently queued support for memory hotremove, which led to some
> new corner cases for kexec.
>
> If the kexec segments are loaded for a removable region, that region may
> be removed before kexec actually occurs. This causes the
Hello!
arm64 recently queued support for memory hotremove, which led to some
new corner cases for kexec.
If the kexec segments are loaded for a removable region, that region may
be removed before kexec actually occurs. This causes the first kernel to
lockup when applying the relocations. (I've
15 matches
Mail list logo