On Mon, Apr 12, 2021 at 7:12 AM Alex Ghiti wrote:
>
> Le 4/9/21 à 10:42 AM, Vitaly Wool a écrit :
> > On Fri, Apr 9, 2021 at 3:59 PM Mike Rapoport wrote:
> >>
> >> On Fri, Apr 09, 2021 at 02:46:17PM +0200, David Hildenbrand wrote:
> >> Also, will that memory properly be exposed in the resourc
Le 4/9/21 à 10:42 AM, Vitaly Wool a écrit :
On Fri, Apr 9, 2021 at 3:59 PM Mike Rapoport wrote:
On Fri, Apr 09, 2021 at 02:46:17PM +0200, David Hildenbrand wrote:
Also, will that memory properly be exposed in the resource tree as
System RAM (e.g., /proc/iomem) ? Otherwise some things (/proc/k
On Fri, Apr 9, 2021 at 3:59 PM Mike Rapoport wrote:
>
> On Fri, Apr 09, 2021 at 02:46:17PM +0200, David Hildenbrand wrote:
> > > > > Also, will that memory properly be exposed in the resource tree as
> > > > > System RAM (e.g., /proc/iomem) ? Otherwise some things (/proc/kcore)
> > > > > won't wor
On 09.04.21 16:10, Mike Rapoport wrote:
On Fri, Apr 09, 2021 at 02:07:24PM +0200, David Hildenbrand wrote:
On 09.04.21 13:39, Alex Ghiti wrote:
Hi David,
I assume you still somehow create the direct mapping for the kernel, right?
So it's really some memory region with a direct mapping but wit
On Fri, Apr 09, 2021 at 02:07:24PM +0200, David Hildenbrand wrote:
> On 09.04.21 13:39, Alex Ghiti wrote:
> > Hi David,
>
> I assume you still somehow create the direct mapping for the kernel, right?
> So it's really some memory region with a direct mapping but without a memmap
> (and right now, w
> Am 09.04.2021 um 15:59 schrieb Mike Rapoport :
>
> On Fri, Apr 09, 2021 at 02:46:17PM +0200, David Hildenbrand wrote:
> Also, will that memory properly be exposed in the resource tree as
> System RAM (e.g., /proc/iomem) ? Otherwise some things (/proc/kcore)
> won't work as expecte
On Fri, Apr 09, 2021 at 02:46:17PM +0200, David Hildenbrand wrote:
> > > > Also, will that memory properly be exposed in the resource tree as
> > > > System RAM (e.g., /proc/iomem) ? Otherwise some things (/proc/kcore)
> > > > won't work as expected - the kernel won't be included in a dump.
> > Do
Le 4/9/21 à 8:07 AM, David Hildenbrand a écrit :
On 09.04.21 13:39, Alex Ghiti wrote:
Hi David,
Le 4/9/21 à 4:23 AM, David Hildenbrand a écrit :
On 09.04.21 09:14, Alex Ghiti wrote:
Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
From: Vitaly Wool
Introduce XIP (eXecute In Place) support fo
Also, will that memory properly be exposed in the resource tree as
System RAM (e.g., /proc/iomem) ? Otherwise some things (/proc/kcore)
won't work as expected - the kernel won't be included in a dump.
Do we really need a XIP kernel to included in kdump?
And does not it sound weird to expose fl
On Fri, Apr 09, 2021 at 07:39:59AM -0400, Alex Ghiti wrote:
> Hi David,
>
> Le 4/9/21 à 4:23 AM, David Hildenbrand a écrit :
> > On 09.04.21 09:14, Alex Ghiti wrote:
> > > Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
> > > > From: Vitaly Wool
> > > >
> > > > Introduce XIP (eXecute In Place) su
On 09.04.21 13:39, Alex Ghiti wrote:
Hi David,
Le 4/9/21 à 4:23 AM, David Hildenbrand a écrit :
On 09.04.21 09:14, Alex Ghiti wrote:
Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
From: Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms.
It allows code to be executed
Hi David,
Le 4/9/21 à 4:23 AM, David Hildenbrand a écrit :
On 09.04.21 09:14, Alex Ghiti wrote:
Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
From: Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms.
It allows code to be executed directly from non-volatile storage
dir
On 09.04.21 09:14, Alex Ghiti wrote:
Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
From: Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms.
It allows code to be executed directly from non-volatile storage
directly addressable by the CPU, such as QSPI NOR flash which ca
Le 4/9/21 à 2:51 AM, Alexandre Ghiti a écrit :
From: Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms.
It allows code to be executed directly from non-volatile storage
directly addressable by the CPU, such as QSPI NOR flash which can
be found on many RISC-V platforms. T
From: Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms.
It allows code to be executed directly from non-volatile storage
directly addressable by the CPU, such as QSPI NOR flash which can
be found on many RISC-V platforms. This makes way for significant
optimization of RAM
15 matches
Mail list logo
