Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiang Jilin <freephp@gmail.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Hui Zhu <teawater@gmail.com>,
	gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add xgetbv/xsetbv instructions support for precord.
Date: Tue, 13 Oct 2009 08:48:00 -0000	[thread overview]
Message-ID: <7d77a27d0910130148k4afee99en67ac2f3bff35d73b@mail.gmail.com> (raw)
In-Reply-To: <4AD34D7C.2030309@vmware.com>

On Mon, Oct 12, 2009 at 11:38 PM, Michael Snyder <msnyder@vmware.com> wrote:
> Jiang Jilin wrote:
>>
>> Hi Michael,
>>
>> Is this small patch acceptable? If yes, please tell me who can help me
>> check it in,
>> you know, I've no write permission.
>
> Cool, I think Hui, Joel and I all approved this patch.
> I'll check it in -- consider it committed.

Thank you all!

>> On Sat, Oct 10, 2009 at 6:22 AM, Michael Snyder <msnyder@vmware.com>
>> wrote:
>>>
>>> Jiang Jilin wrote:
>>>>
>>>> 2009-10-09  Jiang Jilin  <freephp@gmail.com>
>>>>
>>>>       * i386-tdep.c (i386_process_record): Add xgetbv/xsetbv
>>>> instructions
>>>> support
>>>> ---
>>>>  gdb/i386-tdep.c |   13 +++++++++++++
>>>>  1 files changed, 13 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
>>>> index b79bcd2..1efe07f 100644
>>>> --- a/gdb/i386-tdep.c
>>>> +++ b/gdb/i386-tdep.c
>>>> @@ -5172,6 +5172,19 @@ reswitch:
>>>>         break;
>>>>         /* lgdt */
>>>>       case 2:
>>>> +         if (ir.mod == 3)
>>>> +           {
>>>> +             /* xgetbv */
>>>> +             if (ir.rm == 0)
>>>> +               {
>>>> +                 I386_RECORD_ARCH_LIST_ADD_REG
>>>> (X86_RECORD_REAX_REGNUM);
>>>> +                 I386_RECORD_ARCH_LIST_ADD_REG
>>>> (X86_RECORD_REDX_REGNUM);
>>>> +                 break;
>>>> +               }
>>>> +             /* xsetbv */
>>>> +             else if (ir.rm == 1)
>>>> +               break;
>>>> +           }
>>>>         /* lidt */
>>>>       case 3:
>>>>         if (ir.mod == 3)
>>>
>>> Jiang (is that how you would like to be addressed?)
>>>
>>> This change looks OK to me in principle, but I'm not qualified
>>> to judge its technical correctness.  I would like to get Hui
>>> Zhu's opinion.
>>>
>>> Nice job on the formatting and coding conventions!
>>> ;-)
>>>
>>> Michael
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>



-- 
Jiang


      reply	other threads:[~2009-10-13  8:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 13:37 Jiang Jilin
2009-10-09 17:21 ` Joel Brobecker
     [not found]   ` <7d77a27d0910091838l76217714m92a55afc2fdf25f3@mail.gmail.com>
2009-10-10  2:33     ` Joel Brobecker
2009-10-10  2:46       ` Jiang Jilin
2009-10-10  4:59         ` Joel Brobecker
2009-10-10  7:57       ` Hui Zhu
2009-10-10  8:10         ` Jiang Jilin
2009-10-10  8:14         ` Jiang Jilin
2009-10-09 22:26 ` Michael Snyder
2009-10-12  8:00   ` Jiang Jilin
2009-10-12 15:43     ` Michael Snyder
2009-10-13  8:48       ` Jiang Jilin [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=7d77a27d0910130148k4afee99en67ac2f3bff35d73b@mail.gmail.com \
    --to=freephp@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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