From: "Sturm, Michael" <michael.sturm@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] Add support for Intel PKRU register to GDB and GDBserver.
Date: Fri, 03 Feb 2017 09:20:00 -0000 [thread overview]
Message-ID: <58944B56.9070603@intel.com> (raw)
In-Reply-To: <8360kuvz1d.fsf@gnu.org>
Thank you , Eli!
Thanks and Regards,
Michael
On 01/02/2017 14:08, Eli Zaretskii wrote:
>> From: Michael Sturm <michael.sturm@intel.com>
>> Cc: gdb-patches@sourceware.org, michael.sturm@intel.com
>> Date: Wed, 1 Feb 2017 14:03:25 +0100
>>
>> This patch adds support for the registers added by the
>> Memory Protection Keys for Userspace (PKU aka PKEYs) feature.
>> Native and remote debugging are covered by this patch.
>>
>> The XSAVE area is extended with a new state containing
>> the 32-bit wide PKRU register. The new register is added to
>> amd64-avx-mpx_avx512-* tdesc, thus it is renamed accordingly. Also,
>> respective xstate mask X86_XSTATE_AVX_MPX_AVX512_MASK is renamed to
>> X86_XSTATE_AVX_MPX_AVX512_PKU_MASK to reflect the new feature set
>> it supports.
>>
>> For more information, please refer to the
>> Intel(R) 64 and IA-32 Architectures Software Developer's
>> Manual - Septemper 2015
>> http://www.intel.com/content/dam/www/public/us/en/documents/
>> manuals/64-ia-32-architectures-software-developer-manual-325462.pdf
> OK for the documentation parts.
>
> Thanks.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2017-02-03 9:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:04 [PATCH v4 0/5] Add support for PKRU register to GDB and GDBServer Michael Sturm
2017-02-01 13:03 ` [PATCH 1/5] Sync up x86-gcc-cpuid.h with cpuid.h from gcc-6 branch Michael Sturm
2017-02-01 13:03 ` [PATCH 2/5] Change xstate_bv handling to use 8 bytes of data Michael Sturm
2017-02-01 13:03 ` [PATCH 3/5] Rename target descriptions to reflect actual content of description Michael Sturm
2017-02-01 13:04 ` [PATCH 4/5] Add target description for avx-avx512 Michael Sturm
2017-02-10 15:44 ` Pedro Alves
2017-02-01 13:04 ` [PATCH 5/5] Add support for Intel PKRU register to GDB and GDBserver Michael Sturm
2017-02-01 13:09 ` Eli Zaretskii
2017-02-03 9:20 ` Sturm, Michael [this message]
2017-02-10 15:46 ` Pedro Alves
2017-06-19 20:15 ` Simon Marchi
2017-06-20 7:07 ` Tedeschi, Walfred
2017-06-20 8:49 ` Simon Marchi
2017-06-20 10:07 ` Yao Qi
2017-06-20 10:53 ` Tedeschi, Walfred
2017-06-20 11:03 ` Yao Qi
2017-06-20 11:04 ` Tedeschi, Walfred
2017-06-22 11:17 ` Tedeschi, Walfred
[not found] ` <CAH=s-POWw-duRWLMAGrU_gqWfH5HEo9eCiRK-y7NgBt8jFp0_Q@mail.gmail.com>
2017-06-22 11:53 ` Tedeschi, Walfred
2017-02-07 14:29 ` [ping][PATCH v4 0/5] Add support for PKRU register to GDB and GDBServer Sturm, Michael
2017-02-17 13:47 ` [pushed] " Sturm, Michael
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=58944B56.9070603@intel.com \
--to=michael.sturm@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@redhat.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