On Thu, Feb 21, 2019 at 07:55:46PM +0100, Heinrich Schuchardt wrote:
> On 2/21/19 11:21 AM, Alexander Graf wrote:
> > On 02/20/2019 07:12 PM, Heinrich Schuchardt wrote:
> >> On 2/18/19 1:52 AM, AKASHI Takahiro wrote:
> >>> Heinrich,
> >>>
> >>> On Sat, Feb 16, 2019 at 08:50:43PM +0100, Heinrich Sch
On 2/21/19 11:21 AM, Alexander Graf wrote:
> On 02/20/2019 07:12 PM, Heinrich Schuchardt wrote:
>> On 2/18/19 1:52 AM, AKASHI Takahiro wrote:
>>> Heinrich,
>>>
>>> On Sat, Feb 16, 2019 at 08:50:43PM +0100, Heinrich Schuchardt wrote:
All code and data sections of PE images are already in the co
On 02/20/2019 07:12 PM, Heinrich Schuchardt wrote:
On 2/18/19 1:52 AM, AKASHI Takahiro wrote:
Heinrich,
On Sat, Feb 16, 2019 at 08:50:43PM +0100, Heinrich Schuchardt wrote:
All code and data sections of PE images are already in the correct relative
location when loaded into memory. There is no
On 2/18/19 1:52 AM, AKASHI Takahiro wrote:
> Heinrich,
>
> On Sat, Feb 16, 2019 at 08:50:43PM +0100, Heinrich Schuchardt wrote:
>> All code and data sections of PE images are already in the correct relative
>> location when loaded into memory. There is not need to copy them once
>> again.
>
> Whi
Heinrich,
On Sat, Feb 16, 2019 at 08:50:43PM +0100, Heinrich Schuchardt wrote:
> All code and data sections of PE images are already in the correct relative
> location when loaded into memory. There is not need to copy them once
> again.
While I'm not very familiar with how PE image is created (i
All code and data sections of PE images are already in the correct relative
location when loaded into memory. There is not need to copy them once
again.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_image_loader.c | 64 ++-
1 file changed, 11 insertions(+)
All code and data sections of PE images are already in the correct relative
location when loaded into memory. There is not need to copy them once
again.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_image_loader.c | 64 ++-
1 file changed, 11 insertions(+)
7 matches
Mail list logo