qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: chrisw@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
	qemu-devel@nongnu.org, blauwirbel@gmail.com, ddutile@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] RAM API: Make use of it for x86 PC
Date: Tue, 16 Nov 2010 08:58:29 -0600	[thread overview]
Message-ID: <4CE29C15.7040704@codemonkey.ws> (raw)
In-Reply-To: <20101101151415.3927.87944.stgit@s20.home>

On 11/01/2010 10:14 AM, Alex Williamson wrote:
> Register the actual VM RAM using the new API
>
> Signed-off-by: Alex Williamson<alex.williamson@redhat.com>
> ---
>
>   hw/pc.c |   12 ++++++------
>   1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/hw/pc.c b/hw/pc.c
> index 69b13bf..0ea6d10 100644
> --- a/hw/pc.c
> +++ b/hw/pc.c
> @@ -912,14 +912,14 @@ void pc_memory_init(ram_addr_t ram_size,
>       /* allocate RAM */
>       ram_addr = qemu_ram_alloc(NULL, "pc.ram",
>                                 below_4g_mem_size + above_4g_mem_size);
> -    cpu_register_physical_memory(0, 0xa0000, ram_addr);
> -    cpu_register_physical_memory(0x100000,
> -                 below_4g_mem_size - 0x100000,
> -                 ram_addr + 0x100000);
> +
> +    qemu_ram_register(0, 0xa0000, ram_addr);
> +    qemu_ram_register(0x100000, below_4g_mem_size - 0x100000,
> +                      ram_addr + 0x100000);
>   #if TARGET_PHYS_ADDR_BITS>  32
>       if (above_4g_mem_size>  0) {
> -        cpu_register_physical_memory(0x100000000ULL, above_4g_mem_size,
> -                                     ram_addr + below_4g_mem_size);
> +        qemu_ram_register(0x100000000ULL, above_4g_mem_size,
> +                          ram_addr + below_4g_mem_size);
>       }
>    

Take a look at the memory shadowing in the i440fx.  The regions of 
memory in the BIOS area can temporarily become RAM.

That's because there is normally RAM backing this space but the memory 
controller redirects writes to the ROM space.

Not sure the best way to handle this, but the basic concept is, RAM 
always exists but if a device tries to access it, it may or may not be 
accessible as RAM at any given point in time.

Regards,

Anthony Liguori

>   #endif
>
>
>
>
>    

  reply	other threads:[~2010-11-16 14:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 16:38 [Qemu-devel] [PATCH 0/2] Minimal RAM API support Alex Williamson
2010-10-29 16:39 ` [Qemu-devel] [PATCH 1/2] " Alex Williamson
2010-10-29 19:57   ` Blue Swirl
2010-10-29 20:15     ` Alex Williamson
2010-11-01  2:17   ` Isaku Yamahata
2010-11-01  2:32     ` Alex Williamson
2010-10-29 16:39 ` [Qemu-devel] [PATCH 2/2] RAM API: Make use of it for x86 PC Alex Williamson
2010-11-01 15:13 ` [Qemu-devel] [PATCH v2 0/2] Minimal RAM API support Alex Williamson
2010-11-01 15:14   ` [Qemu-devel] [PATCH v2 1/2] " Alex Williamson
2010-11-16 14:55     ` Anthony Liguori
2010-11-16 15:02       ` Alexander Graf
2010-11-16 15:08         ` Anthony Liguori
2010-11-01 15:14   ` [Qemu-devel] [PATCH v2 2/2] RAM API: Make use of it for x86 PC Alex Williamson
2010-11-16 14:58     ` Anthony Liguori [this message]
2010-11-16 21:24       ` Alex Williamson
2010-11-17  9:31         ` Gleb Natapov
2010-11-17 23:42         ` Anthony Liguori
2010-11-18 15:22           ` Avi Kivity
2010-11-18 15:46             ` Anthony Liguori
2010-11-18 15:57               ` Avi Kivity
2010-11-18 16:09                 ` Anthony Liguori
2010-11-18 16:18                   ` Avi Kivity
2010-11-18 16:35                     ` Michael S. Tsirkin
2010-11-18 15:51           ` Gleb Natapov
2010-11-18 21:41   ` [Qemu-devel] [PATCH v3 0/2] Minimal RAM API support Alex Williamson
2010-11-18 21:41     ` [Qemu-devel] [PATCH v3 1/2] " Alex Williamson
2010-11-18 21:41     ` [Qemu-devel] [PATCH v3 2/2] RAM API: Make use of it for x86 PC Alex Williamson

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=4CE29C15.7040704@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=alex.williamson@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=chrisw@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.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).