From: Alexander Graf <agraf@csgraf.de>
To: Paolo Bonzini <pbonzini@redhat.com>, Cameron Esfahani <dirty@apple.com>
Cc: Roman Bolshakov <r.bolshakov@yadro.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] hvf: Avoid mapping regions < PAGE_SIZE as ram
Date: Mon, 25 Oct 2021 21:10:26 +0200 [thread overview]
Message-ID: <a19cfe8f-a013-b2da-7893-50d7c1ecfecd@csgraf.de> (raw)
In-Reply-To: <6c9b6035-276c-1e15-7b7f-81094473368b@redhat.com>
On 25.10.21 19:11, Paolo Bonzini wrote:
> On 25/10/21 10:25, Alexander Graf wrote:
>> HVF has generic memory listener code that adds all RAM regions as HVF
>> RAM
>> regions. However, HVF can only handle page aligned, page granule
>> regions.
>>
>> So let's ignore regions that are not page aligned and sized. They
>> will be
>> trapped as MMIO instead.
>>
>> Signed-off-by: Alexander Graf <agraf@csgraf.de>
>> ---
>> accel/hvf/hvf-accel-ops.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/accel/hvf/hvf-accel-ops.c b/accel/hvf/hvf-accel-ops.c
>> index 6bf319d34c..090155853a 100644
>> --- a/accel/hvf/hvf-accel-ops.c
>> +++ b/accel/hvf/hvf-accel-ops.c
>> @@ -135,6 +135,12 @@ static void hvf_set_phys_mem(MemoryRegionSection
>> *section, bool add)
>> }
>> }
>> + if (int128_get64(section->size) & (qemu_real_host_page_size -
>> 1) ||
>> + section->offset_within_address_space &
>> (qemu_real_host_page_size - 1)) {
>> + /* Not page aligned, so we can not map as RAM */
>> + add = false;
>> + }
>> +
>> mem = hvf_find_overlap_slot(
>> section->offset_within_address_space,
>> int128_get64(section->size));
>>
>
> Queued, thanks.
You probably want v2 instead :)
Alex
next prev parent reply other threads:[~2021-10-25 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 8:25 [PATCH] hvf: Avoid mapping regions < PAGE_SIZE as ram Alexander Graf
2021-10-25 10:56 ` Philippe Mathieu-Daudé
2021-10-25 17:11 ` Paolo Bonzini
2021-10-25 19:10 ` Alexander Graf [this message]
2021-10-26 16:34 ` Paolo Bonzini
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=a19cfe8f-a013-b2da-7893-50d7c1ecfecd@csgraf.de \
--to=agraf@csgraf.de \
--cc=dirty@apple.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
/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).