* [Qemu-devel] Reserve physical memory region in QEMU
@ 2015-08-25 3:16 Naman patel
2015-08-25 3:21 ` Naman patel
0 siblings, 1 reply; 2+ messages in thread
From: Naman patel @ 2015-08-25 3:16 UTC (permalink / raw)
To: QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
Hi,
My requirement is to have a reserved physical memory region for QEMU
that can be written using *cpu_physical_memory_region(),* which then can
also be used by the linux kernel for reading and writing. How can one
reserve such memory region in QEMU 2.0? And what care should one take while
doing this?
Regards,
Naman
[-- Attachment #2: Type: text/html, Size: 753 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [Qemu-devel] Reserve physical memory region in QEMU
2015-08-25 3:16 [Qemu-devel] Reserve physical memory region in QEMU Naman patel
@ 2015-08-25 3:21 ` Naman patel
0 siblings, 0 replies; 2+ messages in thread
From: Naman patel @ 2015-08-25 3:21 UTC (permalink / raw)
To: QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Extremely sorry, my bad, its *cpu_physical_memory_write() *function to be
precise.
Regards,
Naman
On Tue, Aug 25, 2015 at 8:46 AM, Naman patel <naman321@gmail.com> wrote:
> Hi,
> My requirement is to have a reserved physical memory region for QEMU
> that can be written using *cpu_physical_memory_region(),* which then can
> also be used by the linux kernel for reading and writing. How can one
> reserve such memory region in QEMU 2.0? And what care should one take while
> doing this?
>
>
> Regards,
> Naman
>
[-- Attachment #2: Type: text/html, Size: 1816 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-08-25 3:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-25 3:16 [Qemu-devel] Reserve physical memory region in QEMU Naman patel
2015-08-25 3:21 ` Naman patel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).