From: Avi Kivity <avi@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>, TeLeMan <geleman@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] TCG: Fix TB invalidation after breakpoint insertion/deletion
Date: Thu, 24 May 2012 17:26:32 +0300 [thread overview]
Message-ID: <4FBE4518.4000402@redhat.com> (raw)
In-Reply-To: <CAMo8BfJx6V2e4qKQOMXtTQE4W1JCrEMLKvxPqybE4LjQ-FZ+Ow@mail.gmail.com>
On 05/24/2012 05:11 PM, Max Filippov wrote:
>>
>> Not in breakpoint_invalidate as the missing offset was compensated
>> before your commit (well, starting with c2f07f81a2 in fact).
>
> I'd say that compensation that you mention
>
> ram_addr = (memory_region_get_ram_addr(section.mr)
> + section.offset_within_region) & TARGET_PAGE_MASK;
> this >>>> ram_addr |= (pc & ~TARGET_PAGE_MASK);
> tb_invalidate_phys_page_range(ram_addr, ram_addr + 1, 0);
>
> was removed by f3705d53296d, not by 1e7855a558
Indeed. Note how the |= cleverly accommodates both truncating and
non-truncating cpu_get_phys_page_debug().
>
>> But it looks like cpu_get_phys_page_debug was broken for quite a while.
>> Let's fix those archs to return more than page-aligned addresses.
>
> You mean make them all return full physical address?
> I'd propose to rename the function then as well.
>
Agree to both. cpu_translate_virtual_address() or similar would be more
explanatory IMO.
btw, how does the thing work for soft-tlb cpus? It looks like this
thing should trigger on tlb loads, not when the breakpoint is set. This
is true for hardware page tables as well, as the mapping can change,
though it's less likely.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-24 14:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 2:34 [Qemu-devel] [PATCH] TCG: Fix TB invalidation after breakpoint insertion/deletion Jan Kiszka
2012-05-24 2:44 ` Jan Kiszka
2012-05-24 10:51 ` Max Filippov
2012-05-24 11:25 ` Jan Kiszka
2012-05-24 12:08 ` Max Filippov
2012-05-24 12:16 ` Jan Kiszka
2012-05-24 12:42 ` Max Filippov
2012-05-24 13:26 ` Jan Kiszka
2012-05-24 14:11 ` Max Filippov
2012-05-24 14:21 ` Jan Kiszka
2012-05-24 14:29 ` Max Filippov
2012-05-24 14:34 ` Jan Kiszka
2012-05-24 14:26 ` Avi Kivity [this message]
2012-05-24 19:58 ` Max Filippov
2012-05-28 9:34 ` Avi Kivity
2012-05-28 11:54 ` Max Filippov
2012-05-28 12:04 ` Avi Kivity
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=4FBE4518.4000402@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=geleman@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jcmvbkbc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.