Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdb/x86: Handle kernels using compact xsave format
Date: Thu, 03 May 2018 17:37:00 -0000	[thread overview]
Message-ID: <20180503173712.GI3375@embecosm.com> (raw)
In-Reply-To: <6131c1b9-21c1-6a38-f466-34bfef144a26@redhat.com>

* Pedro Alves <palves@redhat.com> [2018-05-03 18:11:15 +0100]:

> On 05/03/2018 06:06 PM, Andrew Burgess wrote:
> > This patch is a follow-up for this patch:
> > 
> >   https://sourceware.org/ml/gdb-patches/2018-03/msg00275.html
> 
> Can you summarize what changed in this version?

Of course, sorry, I should have thought to do that.

The original patch focused entirely on the fctrl register, which is
where I saw the original problem.

When I revisited the patch I realised that there's nothing special
about that register, it was _all_ of the x87 control registers, that
are broken (and mxcsr).

So the biggest change is that after this patch _no_ registers are read
from the xsave buffer unless the relevant feature is enabled.

And _no_ register will be written back to the xsave buffer unless the
value has been modified.

I did manage to remove a '{ .... }' nesting level in this patch which
means I've updated the indentation on a bunch of code.

The patch also covers gdbserver, which the original patch didn't.

Hope that helps,

Thanks,
Andrew


  reply	other threads:[~2018-05-03 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 17:06 Andrew Burgess
2018-05-03 17:11 ` Pedro Alves
2018-05-03 17:37   ` Andrew Burgess [this message]
2018-05-04 10:39     ` Pedro Alves
2018-05-04 19:14       ` Andrew Burgess
2018-05-04 19:23         ` Pedro Alves

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=20180503173712.GI3375@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --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