qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Jim Wilson <jimw@sifive.com>
Cc: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
	"lvivier@redhat.com" <lvivier@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"amarkovic@wavecomp.com" <amarkovic@wavecomp.com>,
	Aleksandar Rikalo <arikalo@wavecomp.com>
Subject: Re: [Qemu-devel] [PATCH v10 3/3] linux-user: Add support for statx() syscall
Date: Wed, 19 Jun 2019 01:13:00 +0200	[thread overview]
Message-ID: <CAL1e-=iArKHT+pVe5uT1v800=pGuMLB=SGpuBAZouq5-0ekfGA@mail.gmail.com> (raw)
In-Reply-To: <121c4da9-bf13-0da3-39a9-22891dabcb5c@sifive.com>

On Wednesday, June 19, 2019, Jim Wilson <jimw@sifive.com> wrote:

> On 6/7/19 3:35 AM, Aleksandar Markovic wrote:
>
>> Implement support for translation of system call statx().
>>
>
> I also need these patches for 32-bit RISC-V linux user mode support.
>
> glibc ld.so calls statx if fstatat is not supported.  Apparently new linux
> architecture ports aren't allowed to define __ARCH_WANT_NEW_STAT which
> enables fstatat because this is already obsolete.  64-bit RISC-V linux does
> have fstatat, but apparently this was a mistake which we can't fix now
> because the ABI is already frozen.  The 32-bit RISC-V ABI is not frozen
> yet, so it won't have fstatat.  Anyways, without statx, ld.so doesn't work,
> which makes user mode qemu pretty useless, so we do need this emulated in
> qemu to make the 32-bit RISC-V linux user mode support work properly.
>
>
Jim, Aleksandar Rikalo, the author of the patch was about to send Laurent
explanation why this aproach is needed in its current organization, on a
very similar line of reasoning as yours.

I am waiting on him to send a new version of the series. Meanwhile you can
send strace patch to the list, and I can even incude it in my series after
and together with Aleksandar's patch, if you don't object.

Yours,

Aleksandar M.

I started with the August 2018 version of the patch a few weeks ago, and
> just noticed that it has been resubmitted.  I had to modify the patch
> slightly to apply to current sources, and had to fix one bug to make it
> work.  The line
> +                if (ret != TARGET_ENOSYS) {
> needs to instead be
> +                if (ret != -TARGET_ENOSYS) {
> I see that Laurent has already pointed that out.
>
> Incidentally, I also have strace patches for statx that work on top of
> this patch, since I didn't see that in the nanomips patch set I started
> with.  That helped me debug the 32-bit RISC-V user mode support.
>
> I've tested this on Ubuntu 16.04 (no host statx) and Ubuntu 19.10 (with
> host statx) and it worked well for me running the gcc testsuite for a
> riscv32-linux target.  I haven't tried testing the latest version of the
> patch yet.  I can do that if this is helpful.
>
> Jim
>
>

  reply	other threads:[~2019-06-18 23:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 10:35 [Qemu-devel] [PATCH v10 0/3] linux-user: A set of miscellaneous patches Aleksandar Markovic
2019-06-07 10:35 ` [Qemu-devel] [PATCH v10 1/3] linux-user: Add support for setsockopt() options IPV6_<ADD|DROP>_MEMBERSHIP Aleksandar Markovic
2019-06-12 16:47   ` Laurent Vivier
2019-06-07 10:35 ` [Qemu-devel] [PATCH v10 2/3] linux-user: Add support for setsockopt() option SOL_ALG Aleksandar Markovic
2019-06-13 10:05   ` Laurent Vivier
2019-06-07 10:35 ` [Qemu-devel] [PATCH v10 3/3] linux-user: Add support for statx() syscall Aleksandar Markovic
2019-06-13 10:46   ` Laurent Vivier
2019-06-19 12:12     ` Aleksandar Rikalo
2019-06-19 12:56       ` Laurent Vivier
2019-06-18 22:06   ` Jim Wilson
2019-06-18 23:13     ` Aleksandar Markovic [this message]
2019-06-19  0:23       ` Jim Wilson
2019-06-11  9:30 ` [Qemu-devel] [PATCH v10 0/3] linux-user: A set of miscellaneous patches Aleksandar Markovic

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='CAL1e-=iArKHT+pVe5uT1v800=pGuMLB=SGpuBAZouq5-0ekfGA@mail.gmail.com' \
    --to=aleksandar.m.mail@gmail.com \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.com \
    --cc=jimw@sifive.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).