All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
	xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/gdbsx: fix 'g' packet response for 64bit guests
Date: Tue, 31 Jul 2018 18:10:07 +0200	[thread overview]
Message-ID: <20180731161007.GR1371@mail-itl> (raw)
In-Reply-To: <20180731090024.xbovqmyfrj6xiaid@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1053 bytes --]

On Tue, Jul 31, 2018 at 10:00:24AM +0100, Wei Liu wrote:
> On Tue, Jul 31, 2018 at 04:30:42AM +0200, Marek Marczykowski-Górecki wrote:
> > --- a/tools/debugger/gdbsx/gx/gx_local.c
> > +++ b/tools/debugger/gdbsx/gx/gx_local.c
> > @@ -45,8 +45,8 @@ prnt_32regs(struct xg_gdb_regs32 *r32p)
> >  static void
> >  prnt_64regs(struct xg_gdb_regs64 *r64p)
> >  {
> > -    printf("rip:"XGF64" rsp:"XGF64" flags:"XGF64"\n", r64p->rip, r64p->rsp,
> > -           r64p->rflags);
> > +    printf("rip:"XGF64" rsp:"XGF64" flags:%08x\n", r64p->rip, r64p->rsp,
> > +           r64p->eflags);
> 
> I think it would be better to introduce XGF32 and XGFM32 in the header.

I was inspired by prnt_32regs function, which use explicit %08x. Should
it be changed there too (to PRIx32)? Otherwise that would be
inconsistent (and maybe warrant a totally separate cleanup).

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-07-31 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31  2:30 [PATCH] tools/gdbsx: fix 'g' packet response for 64bit guests Marek Marczykowski-Górecki
2018-07-31  8:01 ` Jan Beulich
2018-07-31  8:09   ` Andrew Cooper
2018-07-31  8:35     ` Jan Beulich
2018-07-31 16:04   ` Marek Marczykowski
2018-07-31  9:00 ` Wei Liu
2018-07-31  9:08   ` Andrew Cooper
2018-07-31  9:12     ` Wei Liu
2018-07-31 16:10   ` Marek Marczykowski-Górecki [this message]
2018-07-31 16:28     ` Wei Liu
2018-07-31 16:29     ` Andrew Cooper

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=20180731161007.GR1371@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.