From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Marek Dolata - mkdolata@us.ibm.com" <mkdolata@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
Doug Gale <doug16k@gmail.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] /target/i386: fix gdbstub k_gs_base issue
Date: Fri, 27 Dec 2019 20:14:48 +0100 [thread overview]
Message-ID: <f29f72e8-8b80-c064-599a-a706979a425b@redhat.com> (raw)
In-Reply-To: <f392e1a15634455d8af668b28b88f3b4@us.ibm.com>
Hi Marek,
If you look at the other patches, you'll notice no leading slash is
used, so please remove it when resending.
Maybe you can use "target/i386: Fix handling of k_gs_base register in
32-bit mode in gdbstub" as patch subject.
Please Cc the maintainers. See:
https://wiki.qemu.org/Contribute/SubmitAPatch#CC_the_relevant_maintainer
Doing it for you now (adding Richard and Eduardo).
On 12/27/19 3:41 AM, Marek Dolata - mkdolata@us.ibm.com wrote:
> Fixes: corrects clobbering of registers appearing after k_gs_base
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/1857640
>
> Signed-off-by: Marek Dolata <mkdolata@us.ibm.com>
>
> ---
>
> target/i386/gdbstub.c | 4 +++-
>
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/target/i386/gdbstub.c b/target/i386/gdbstub.c
>
> index aef25b70f1..7228d20674 100644
>
> --- a/target/i386/gdbstub.c
>
> +++ b/target/i386/gdbstub.c
I am having troubles trying to apply your patch:
Applying: /target/i386: fix gdbstub k_gs_base issue
error: corrupt patch at line 23
Patch failed at 0001 /target/i386: fix gdbstub k_gs_base issue
hint: Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
The information on the wiki might help you to use proper format:
https://wiki.qemu.org/Contribute/SubmitAPatch#Use_git_format-patch
>
> @@ -350,14 +350,16 @@ int x86_cpu_gdb_write_register(CPUState *cs,
> uint8_t *mem_buf, int n)
>
> env->segs[R_GS].base = ldl_p(mem_buf);
>
> return 4;
>
> -#ifdef TARGET_X86_64
>
> case IDX_SEG_REGS + 8:
>
> +#ifdef TARGET_X86_64
>
> if (env->hflags & HF_CS64_MASK) {
>
> env->kernelgsbase = ldq_p(mem_buf);
>
> return 8;
>
> }
>
> env->kernelgsbase = ldl_p(mem_buf);
You can add here the
#endif
>
> return 4;
and remove the '#else return 4; #endif' lines.
>
> +#else
>
> + return 4;
>
> #endif
>
> case IDX_FP_REGS + 8:
>
> --
>
> 2.21.0
>
Regards,
Phil.
prev parent reply other threads:[~2019-12-27 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 2:41 [PATCH] /target/i386: fix gdbstub k_gs_base issue Marek Dolata - mkdolata@us.ibm.com
2019-12-27 19:14 ` Philippe Mathieu-Daudé [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=f29f72e8-8b80-c064-599a-a706979a425b@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=doug16k@gmail.com \
--cc=ehabkost@redhat.com \
--cc=mkdolata@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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 NNTP newsgroup(s).