From: Naman patel <naman321@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Reserve physical memory region in QEMU
Date: Tue, 25 Aug 2015 08:51:12 +0530 [thread overview]
Message-ID: <CAAhtxhtA-f0C75PPZfenNbcsOSyo7cAatzq8yMrbJgxs3uFSqQ@mail.gmail.com> (raw)
In-Reply-To: <CAAhtxhseHX-Mx5Mv2T9NbrLCY6w9tU7GkAUXQJ0UnCsqaS9qhg@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2015-08-25 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 3:16 [Qemu-devel] Reserve physical memory region in QEMU Naman patel
2015-08-25 3:21 ` Naman patel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAhtxhtA-f0C75PPZfenNbcsOSyo7cAatzq8yMrbJgxs3uFSqQ@mail.gmail.com \
--to=naman321@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).