From: Richard Weinberger <richard@nod.at>
To: Florian Fainelli <f.fainelli@gmail.com>,
Thomas Meyer <thomas@m3y3r.de>,
linux-kernel@vger.kernel.org
Cc: Jeff Dike <jdike@addtoit.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
"open list:USER-MODE LINUX (UML)"
<user-mode-linux-devel@lists.sourceforge.net>,
"open list:USER-MODE LINUX (UML)"
<user-mode-linux-user@lists.sourceforge.net>
Subject: Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a
Date: Fri, 2 Jun 2017 09:38:45 +0200 [thread overview]
Message-ID: <0effc7cf-7a86-bed6-58cf-d8fd6d3febd6@nod.at> (raw)
In-Reply-To: <3672f56d-da81-1114-f06a-ac99d3680661@gmail.com>
Thomas,
Am 02.06.2017 um 07:49 schrieb Florian Fainelli:
>> the put_fp_registers fails with errno 4 if I recall correctly.
>>
>> I didn't investigate yet further, why the the xstate ptrace call fails.
>
> Which of the branches is put_fp_registers() taking? The
> restore_fpx_registers() or restore_fp_registers()? 4 would be EINTR...
> What kernel version is used on your host running the UML binary?
Another question, is this x86_64 UML on a x86_64 host?
Or i386 on x86_64, i386 on i386?
Thanks,
//richard
next prev parent reply other threads:[~2017-06-02 7:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 0:32 Florian Fainelli
2017-05-24 7:02 ` Richard Weinberger
2017-05-24 16:19 ` Florian Fainelli
2017-06-01 19:38 ` Florian Fainelli
2017-06-01 20:11 ` Richard Weinberger
2017-06-01 20:15 ` Florian Fainelli
2017-06-01 20:17 ` Richard Weinberger
2017-06-01 20:40 ` Florian Fainelli
2017-06-01 20:44 ` Richard Weinberger
2017-06-01 20:53 ` Florian Fainelli
2017-06-01 20:58 ` Richard Weinberger
2017-06-01 21:25 ` Thomas Meyer
2017-06-02 5:49 ` Florian Fainelli
2017-06-02 7:38 ` Richard Weinberger [this message]
2017-06-03 21:25 ` Thomas Meyer
2017-06-03 21:36 ` Richard Weinberger
2017-06-02 8:04 ` Thomas Meyer
2017-06-02 8:30 ` Richard Weinberger
2017-06-02 9:15 ` Thomas Meyer
2017-06-02 13:18 ` Thomas Meyer
2017-06-05 19:32 ` Florian Fainelli
2017-06-05 19:34 ` Richard Weinberger
2017-06-28 22:40 ` Florian Fainelli
2017-06-29 7:25 ` Richard Weinberger
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=0effc7cf-7a86-bed6-58cf-d8fd6d3febd6@nod.at \
--to=richard@nod.at \
--cc=f.fainelli@gmail.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®