> For the complete documentation index, see [llms.txt](https://docs.hyperdbg.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperdbg.org/commands/scripting-language/functions/memory/memcpy_pa.md).

# memcpy\_pa

### Function

> memcpy\_pa

### Syntax

> memcpy\_pa( PhysicalDestination, PhysicalSource, Num );

### Parameters

**\[PhysicalDestination]**

A [MASM-like expression](https://docs.hyperdbg.org/commands/scripting-language/assumptions-and-evaluations) to evaluate which is the physical address of the **destination** (physical) buffer.

**\[PhysicalSource]**

A [MASM-like expression](https://docs.hyperdbg.org/commands/scripting-language/assumptions-and-evaluations) to evaluate which is the physical address of the **source** buffer.

**\[Num]**

A [MASM-like expression](https://docs.hyperdbg.org/commands/scripting-language/assumptions-and-evaluations) to evaluate which is the size (length) of the bytes to be copied.

### Description

Copies the contents of the source physical address to the destination (physical) buffer.

### Return value

None

### Examples

`memcpy_pa(6de00000 , @rax, 40);`

Copies **0x40** bytes from the physical buffer pointed by the **RAX** register to the buffer which its physical address is `6de00000`.

### Remarks

Please note that the size argument is passed in the **HEX** format.

Make sure to acquire a spinlock if the destination buffer might be accessed by different cores simultaneously.

This function checks for the validity of both the source and the destination address before performing the copy.

The support for this function is added from **v0.13**.

### Related

[memcpy](https://docs.hyperdbg.org/commands/scripting-language/functions/memory/memcpy)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperdbg.org/commands/scripting-language/functions/memory/memcpy_pa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.