From: Alex Williamson <alex.williamson@redhat.com>
To: "Singh, Brijesh" <brijesh.singh@amd.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Fix the memory region type assignment order
Date: Mon, 4 Feb 2019 10:53:32 -0700 [thread overview]
Message-ID: <20190204105332.73a30073@w520.home> (raw)
In-Reply-To: <20190117215300.29694-2-brijesh.singh@amd.com>
On Thu, 17 Jan 2019 21:53:16 +0000
"Singh, Brijesh" <brijesh.singh@amd.com> wrote:
> Currently, a callback registered through the RAMBlock notifier
> is not able to get the memory region type (i.e callback is not
> able to use memory_region_is_ram_device function). This is
> because mr->ram assignment happens _after_ the memory is allocated
> whereas the callback is executed during allocation.
>
> Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1667249
> Sugegsted-by: Alex Williamson <alex.williamson@redhat.com>
s/Sugegsted/Suggested/
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
> ---
> memory.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/memory.c b/memory.c
> index 61d66e4441..9ec15349dd 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -1652,10 +1652,17 @@ void memory_region_init_ram_device_ptr(MemoryRegion *mr,
> uint64_t size,
> void *ptr)
> {
> - memory_region_init_ram_ptr(mr, owner, name, size, ptr);
> + memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> + mr->terminates = true;
> mr->ram_device = true;
> mr->ops = &ram_device_mem_ops;
> mr->opaque = mr;
> + mr->destructor = memory_region_destructor_ram;
> + mr->dirty_log_mask = tcg_enabled() ? (1 << DIRTY_MEMORY_CODE) : 0;
> + /* qemu_ram_alloc_from_ptr cannot fail with ptr != NULL. */
> + assert(ptr != NULL);
> + mr->ram_block = qemu_ram_alloc_from_ptr(size, ptr, mr, &error_fatal);
> }
>
> void memory_region_init_alias(MemoryRegion *mr,
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
next prev parent reply other threads:[~2019-02-04 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 21:53 [Qemu-devel] [PATCH 0/2] Fix SEV VM device assignment Singh, Brijesh
2019-01-17 21:53 ` [Qemu-devel] [PATCH 2/2] target/i386: sev: Do not pin the ram device memory region Singh, Brijesh
2019-02-04 17:59 ` Alex Williamson
2019-02-04 21:03 ` Singh, Brijesh
2019-01-17 21:53 ` [Qemu-devel] [PATCH 1/2] memory: Fix the memory region type assignment order Singh, Brijesh
2019-02-04 17:53 ` Alex Williamson [this message]
2019-02-04 17:40 ` [Qemu-devel] [PATCH 0/2] Fix SEV VM device assignment Singh, Brijesh
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=20190204105332.73a30073@w520.home \
--to=alex.williamson@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=pbonzini@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).