Re: [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

2018-11-19 Thread Borislav Petkov
On Mon, Nov 19, 2018 at 05:55:15PM +0800, Dave Young wrote: > Another thing is it is not worth to get the exact info, the 1st kernel > reserved part is just fine to be reserved as well in 2nd kernel, no > side effects. Actually there might be some obscure use cases we > do not find which rely

Re: [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

2018-11-19 Thread Borislav Petkov
On Mon, Nov 19, 2018 at 05:55:15PM +0800, Dave Young wrote: > Another thing is it is not worth to get the exact info, the 1st kernel > reserved part is just fine to be reserved as well in 2nd kernel, no > side effects. Actually there might be some obscure use cases we > do not find which rely

Re: [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

2018-11-19 Thread Dave Young
On 11/15/18 at 11:39am, Borislav Petkov wrote: > + Bjorn. > > On Thu, Nov 15, 2018 at 01:44:07PM +0800, lijiang wrote: > > At present, the upstream kernel does not pass the e820 reserved ranges to > > the > > second kernel, which might cause two problems: > > > > The first one is the MMCONFIG

Re: [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

2018-11-19 Thread Dave Young
On 11/15/18 at 11:39am, Borislav Petkov wrote: > + Bjorn. > > On Thu, Nov 15, 2018 at 01:44:07PM +0800, lijiang wrote: > > At present, the upstream kernel does not pass the e820 reserved ranges to > > the > > second kernel, which might cause two problems: > > > > The first one is the MMCONFIG