[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage

From: Jan Kiszka
Subject: Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage
Date: Wed, 23 May 2012 14:36:56 -0300
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv: Gecko/20080226 SUSE/ Thunderbird/ Mnenhy/

On 2012-05-23 13:02, Jan Kiszka wrote:
> On 2012-05-23 11:11, TeLeMan wrote:
>> On Wed, May 23, 2012 at 7:22 PM, Jan Kiszka <address@hidden> wrote:
>>> On 2012-05-23 04:09, TeLeMan wrote:
>>>> On Wed, May 23, 2012 at 11:41 AM, Andreas Färber <address@hidden> wrote:
>>>>> Am 18.05.2012 11:49, schrieb TeLeMan:
>>>>>> This breakage was introduced by the commit "memory: make
>>>>>> phys_page_find() return an unadjusted".
>>>>> You seem to have found the origin of your problem. If you also mention
>>>>> the commit hash in your commit message then certain frontends (gitk,
>>>>> repo.or.cz) will display it as a handy hyperlink to that commit.
>>>>>> Signed-off-by: TeLeMan <address@hidden>
>>>>> Signed-off-by is a legal statement of origin and must not be a pseudonym.
>>>> Ok, please ignore this patch. I won't submit any patch just report bugs.
>>> Then please describe this bug in more details, e.g. how to reproduce.
>> I think its evident. cpu_get_phys_page_debug(env, pc) is not the
>> physical address of pc but the physical page base address of pc.
> ...so this bites us if the instruction spans two pages as
> tb_invalidate_phys_addr requests invalidation on a page granularity.

In fact, this is irrelevant. We only need to flush the address at which
the instruction starts, and that is achieved by flushing all TB that
relate to that page as the current code does.

So, again my question: How can I reproduce the issue you see?


Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

reply via email to

[Prev in Thread] Current Thread [Next in Thread]