On 04/18/17 at 02:51pm, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 04/18/17 at 11:47am, Ingo Molnar wrote:
> > > I ported this series to tip:x86/boot (please post future versions against
> > > that),
> > > and beyond a trivial conflict with e820entry => e820_entry,
On 04/18/17 at 02:51pm, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 04/18/17 at 11:47am, Ingo Molnar wrote:
> > > I ported this series to tip:x86/boot (please post future versions against
> > > that),
> > > and beyond a trivial conflict with e820entry => e820_entry, it fails to
> > >
On 04/18/17 at 02:51pm, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 04/18/17 at 11:47am, Ingo Molnar wrote:
> > >
> > > * Baoquan He wrote:
> > >
> > > > People reported kernel panic occurs during system boots up with mem
> > > > boot option.
> > >
On 04/18/17 at 02:51pm, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > On 04/18/17 at 11:47am, Ingo Molnar wrote:
> > >
> > > * Baoquan He wrote:
> > >
> > > > People reported kernel panic occurs during system boots up with mem
> > > > boot option.
> > > > After checking code, several
On 04/18/17 at 02:51pm, Ingo Molnar wrote:
> > > I ported this series to tip:x86/boot (please post future versions against
> > > that),
> > > and beyond a trivial conflict with e820entry => e820_entry, it fails to
> > > build on
> > > 32-bit allmodconfig:
> > >
> > > ld: -r and -shared may
On 04/18/17 at 02:51pm, Ingo Molnar wrote:
> > > I ported this series to tip:x86/boot (please post future versions against
> > > that),
> > > and beyond a trivial conflict with e820entry => e820_entry, it fails to
> > > build on
> > > 32-bit allmodconfig:
> > >
> > > ld: -r and -shared may
* Baoquan He wrote:
> On 04/18/17 at 11:47am, Ingo Molnar wrote:
> >
> > * Baoquan He wrote:
> >
> > > People reported kernel panic occurs during system boots up with mem boot
> > > option.
> > > After checking code, several problems are found about memmap=
* Baoquan He wrote:
> On 04/18/17 at 11:47am, Ingo Molnar wrote:
> >
> > * Baoquan He wrote:
> >
> > > People reported kernel panic occurs during system boots up with mem boot
> > > option.
> > > After checking code, several problems are found about memmap= and mem= in
> > > boot stage
> >
On 04/18/17 at 11:47am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > People reported kernel panic occurs during system boots up with mem boot
> > option.
> > After checking code, several problems are found about memmap= and mem= in
> > boot stage
> > kaslr.
> >
> > *) In
On 04/18/17 at 11:47am, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > People reported kernel panic occurs during system boots up with mem boot
> > option.
> > After checking code, several problems are found about memmap= and mem= in
> > boot stage
> > kaslr.
> >
> > *) In commit
* Baoquan He wrote:
> People reported kernel panic occurs during system boots up with mem boot
> option.
> After checking code, several problems are found about memmap= and mem= in
> boot stage
> kaslr.
>
> *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap=
* Baoquan He wrote:
> People reported kernel panic occurs during system boots up with mem boot
> option.
> After checking code, several problems are found about memmap= and mem= in
> boot stage
> kaslr.
>
> *) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
> one
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot
stage
kaslr.
*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
one memmap
entry is considered and only
People reported kernel panic occurs during system boots up with mem boot option.
After checking code, several problems are found about memmap= and mem= in boot
stage
kaslr.
*) In commit f28442497b5c ("x86/boot: Fix KASLR and memmap= collision"), only
one memmap
entry is considered and only
14 matches
Mail list logo