qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: li guang <lig.fnst@cn.fujitsu.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	ehabkost@redhat.com, jan.kiszka@siemens.com,
	qemu-devel@nongnu.org, blauwirbel@gmail.com, imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/3] target-i386:slightly refactor dr7 related function
Date: Thu, 06 Dec 2012 10:36:06 +0100	[thread overview]
Message-ID: <50C06706.2010808@suse.de> (raw)
In-Reply-To: <1354786064.9165.2.camel@liguang.fnst.cn.fujitsu.com>

Am 06.12.2012 10:27, schrieb li guang:
> 在 2012-12-06四的 09:23 +0000,Peter Maydell写道:
>> On 6 December 2012 09:16, li guang <lig.fnst@cn.fujitsu.com> wrote:
>>> 在 2012-12-06四的 08:54 +0000,Peter Maydell写道:
>>>> On 6 December 2012 03:03, liguang <lig.fnst@cn.fujitsu.com> wrote:
>>>>> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
>>>>> --- a/target-i386/seg_helper.c
>>>>> +++ b/target-i386/seg_helper.c
>>>>> @@ -465,9 +465,9 @@ static void switch_tss(CPUX86State *env, int tss_selector,
>>>>>
>>>>>  #ifndef CONFIG_USER_ONLY
>>>>>      /* reset local breakpoints */
>>>>> -    if (env->dr[7] & 0x55) {
>>>>> -        for (i = 0; i < 4; i++) {
>>>>> -            if (hw_breakpoint_enabled(env->dr[7], i) == 0x1) {
>>>>> +    if (env->dr[7] & DR7_LOCAL_BP_MASK) {
>>>>> +        for (i = 0; i < DR7_MAX_BP; i++) {
>>>>> +            if (hw_breakpoint_enabled(env->dr[7], i)) {
>>>>>                  hw_breakpoint_remove(env, i);
>>>>>              }
>>>>>          }
>>>>
>>>> This is still wrong.
>>>
>>> do you mean the use of 'hw_breakpoint_enabled'? or others?
>>> maybe a mistake, I change it to 'hw_local_breakpoint_enabled'.
>>> if it is I'll re-send a corrected patch.
>>
>> I mean that in the comments on the previous version of this
>> patchseet we explained that this check is specifically checking
>> for whether the breakpoint is enabled locally, and that your
>> change to just returning bool broke this. And in this version
>> of the patch there is still exactly the same problem.
> 
> why broke?
> this function just ask if breakpoint 'i' was enable,
> so we answer enabled or not? 2 simple cases, any problem?

The code comment specifically says "reset local breakpoints". IIUC you
are also resetting global breakpoints, which you shouldn't.

Personally I'd be fine with a hw_local_breakpoint_enabled().

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2012-12-06  9:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06  3:03 [Qemu-devel] [PATCH 1/3] target-i386:define name of breakpoint bit in dr7 liguang
2012-12-06  3:03 ` [Qemu-devel] [PATCH 2/3] target-i386:make hw_breakpoint_enabled return bool type liguang
2012-12-06  3:03 ` [Qemu-devel] [PATCH 3/3] target-i386:slightly refactor dr7 related function liguang
2012-12-06  8:54   ` Peter Maydell
2012-12-06  9:16     ` li guang
2012-12-06  9:23       ` Peter Maydell
2012-12-06  9:27         ` li guang
2012-12-06  9:35           ` 陳韋任 (Wei-Ren Chen)
2012-12-06  9:36           ` Andreas Färber [this message]
2012-12-06  9:48             ` Peter Maydell
2012-12-06  9:57               ` Andreas Färber
2012-12-07  0:53               ` li guang
2012-12-06  9:44           ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2012-12-04  8:11 [Qemu-devel] [PATCH 1/3] target-i386:define name of breakpoint bit in dr7 liguang
2012-12-04  8:11 ` [Qemu-devel] [PATCH 3/3] target-i386:slightly refactor dr7 related function liguang
2012-12-04 18:51   ` Blue Swirl
2012-12-05  0:56     ` li guang
2012-12-05  8:55       ` Jan Kiszka

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=50C06706.2010808@suse.de \
    --to=afaerber@suse.de \
    --cc=blauwirbel@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lig.fnst@cn.fujitsu.com \
    --cc=peter.maydell@linaro.org \
    --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).