From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: walfred.tedeschi@intel.com
Cc: walfred.tedeschi@intel.com, tromey@redhat.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH V7 0/8] Intel(R) MPX register support
Date: Mon, 04 Nov 2013 10:30:00 -0000 [thread overview]
Message-ID: <201311041029.rA4ATxrR007449@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B191B1C36BE@IRSMSX104.ger.corp.intel.com> (walfred.tedeschi@intel.com)
> From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
> Date: Mon, 4 Nov 2013 09:06:06 +0000
>
> Mark,
>
> Do you think the proposal makes sense?
Sorry. No I don't think that makes sense. So I think you should go
ahead and commit your diff as-is (i.e. with both bndN and bndNraw
register names).
Cheers,
Mark
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Tedeschi, Walfred
> Sent: Monday, October 21, 2013 1:33 PM
> To: Mark Kettenis
> Cc: tromey@redhat.com; gdb-patches@sourceware.org
> Subject: RE: [PATCH V7 0/8] Intel(R) MPX register support
>
> Mark,
>
> Our internal users of MPX found it useful to see the raw value, processed values and size together.
> They found out that it was really handy to avoid doing the complement of one for every bound manipulation.
> (I our first patch we changed the type system to add a complement of one type, but this was considered overkill)
>
> In this sense we would like still to display the bounds on a friendly manner to the user. When I say friendly I mean displaying values that are meaningful to the user.
> ->Lower and upper bound should be presented as address format.
> ->No additional manipulation needed to calculate the upper bound limit.
>
> On the other hand we could add the nice display on the python script and eliminate the pseudo register set, having only "bndN".
>
> Would you be ok with such a change?
> (Having the pretty print only on the python side and eliminating the bndraws)
>
>
> Thanks and regards,
> -Fred.
>
> PS: You might use SDE to have an idea how it looks like.
> http://software.intel.com/en-us/articles/using-intel-mpx-with-the-intel-software-development-emulator
> http://software.intel.com/en-us/articles/intel-software-development-emulator
>
>
>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Mark Kettenis
> Sent: Sunday, October 20, 2013 9:23 PM
> To: Tedeschi, Walfred
> Cc: tromey@redhat.com; gdb-patches@sourceware.org; Tedeschi, Walfred
> Subject: Re: [PATCH V7 0/8] Intel(R) MPX register support
>
> > From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> > Cc: gdb-patches@sourceware.org, Walfred Tedeschi
> > <walfred.tedeschi@intel.com>
> >
> > Mark and all,
> >
> > I have noticed no feedback on this patch series.
> > Is there a major change that you would like to see in here?
> >
> > Thanks a lot for your support,
> > Best regards,
> > -Fred
>
> Walfred,
>
> The only thing I'm still somewhat unhappy about the fact that this introduces the "bndNraw" register names in addition to the "bndN"
> names. I think having both the "raw" and "cooked" variants present in GDB's user interface will be confusing. But it is hard to decide what the right interface is for a feature that isn't available in hardware yet and people don't really have any experience with debugging code that uses MPX.
>
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen, Deutschland
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
>
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen, Deutschland
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895
> Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
>
>
>
next prev parent reply other threads:[~2013-11-04 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 12:01 Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 7/8] Add MPX registers tests Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 1/8] Fix conditions in creating a bitfield Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 3/8] Add MPX support for i386 Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 4/8] MPX for amd64 Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 6/8] Add pretty-printer for MPX bnd registers Walfred Tedeschi
2013-10-09 12:01 ` [PATCH V7 8/8] Add MPX feature description to GDB manual Walfred Tedeschi
2013-11-18 20:26 ` Pedro Alves
2013-11-19 8:32 ` Tedeschi, Walfred
2013-10-09 12:01 ` [PATCH V7 5/8] Add MPX support to gdbserver Walfred Tedeschi
2013-11-19 15:14 ` Pedro Alves
2013-11-19 15:43 ` Tedeschi, Walfred
2013-10-09 12:02 ` [PATCH V7 2/8] Add MPX registers XML files Walfred Tedeschi
2013-10-20 19:23 ` [PATCH V7 0/8] Intel(R) MPX register support Mark Kettenis
2013-10-21 11:33 ` Tedeschi, Walfred
2013-11-04 9:07 ` Tedeschi, Walfred
2013-11-04 10:30 ` Mark Kettenis [this message]
2013-11-11 8:24 ` Tedeschi, Walfred
2013-11-11 10:12 ` Mark Kettenis
2013-11-11 11:48 ` Walfred Tedeschi
2013-11-19 10:28 ` Tedeschi, Walfred
2013-11-19 11:13 ` Mark Kettenis
2013-11-19 12:15 ` Tedeschi, Walfred
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=201311041029.rA4ATxrR007449@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=walfred.tedeschi@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).