From: Paolo Bonzini <pbonzini@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>, Fam Zheng <famz@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] exec: Skip mru section if it's a partial page and not resolving subpage
Date: Wed, 15 Nov 2017 22:14:48 +0100 [thread overview]
Message-ID: <e9876d19-3ca6-5be0-572c-b664eddee102@redhat.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1711151930030.26122@zero.eik.bme.hu>
On 15/11/2017 20:00, BALATON Zoltan wrote:
> On Wed, 15 Nov 2017, Paolo Bonzini wrote:
>> This is another possibility:
>>
>> diff --git a/exec.c b/exec.c
>> index 97a24a875e..3bb9fcf257 100644
>> --- a/exec.c
>> +++ b/exec.c
>> @@ -410,22 +410,16 @@ static MemoryRegionSection
>> *address_space_lookup_region(AddressSpaceDispatch *d,
>> {
>> MemoryRegionSection *section = atomic_read(&d->mru_section);
>> subpage_t *subpage;
>> - bool update;
>>
>> - if (section && section !=
>> &d->map.sections[PHYS_SECTION_UNASSIGNED] &&
>> - section_covers_addr(section, addr)) {
>> - update = false;
>> - } else {
>> + if (!section || section ==
>> &d->map.sections[PHYS_SECTION_UNASSIGNED] ||
>> + !section_covers_addr(section, addr)) {
>> section = phys_page_find(d, addr);
>> - update = true;
>> + atomic_set(&d->mru_section, section);
>> }
>> if (resolve_subpage && section->mr->subpage) {
>> subpage = container_of(section->mr, subpage_t, iomem);
>> section =
>> &d->map.sections[subpage->sub_section[SUBPAGE_IDX(addr)]];
>> }
>> - if (update) {
>> - atomic_set(&d->mru_section, section);
>> - }
>> return section;
>> }
>>
>>
>> It will skip the expensive phys_page_find but not the cheap subpage
>> lookup.
>> Does it work for you?
>
> This also works but I can't understand why becuase the problematic call
> to this function which got the wrong result from section_covers_addr was
> with resolve_subpage=false and in that case this looks identical to the
> original which did not work.
The problem was that a resolve_subpage=true mru_section was reused for a
resolve_subpage=false mru_section. This is fixed by always making the
mru_section the same as if resolve_subpage=false (mru_section is set
before looking into the subpage_t).
Thanks,
Paolo
> Unless this function is called multiple
> times and another call with resolve_subpage=true now somehow works
> better with this change or replacing the mru_section earlier before
> subpage lookup makes a difference which is not obvious from this function.
>
> Anyway, it fixes the problem I see so you can use this instead of my patch.
>
> Thank you,
> BALATON Zoltan
prev parent reply other threads:[~2017-11-15 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 22:42 [Qemu-devel] [PATCH] exec: Skip mru section if it's a partial page and not resolving subpage BALATON Zoltan
2017-11-15 13:56 ` Paolo Bonzini
2017-11-15 19:00 ` BALATON Zoltan
2017-11-15 21:14 ` Paolo Bonzini [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=e9876d19-3ca6-5be0-572c-b664eddee102@redhat.com \
--to=pbonzini@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=crosthwaite.peter@gmail.com \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).