qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [GSoC/Outreachy QEMU proposal] Extend support for ioctls in QEMU linux-user mode
Date: Thu, 30 Jan 2020 12:20:50 +0100	[thread overview]
Message-ID: <3d768689-b69f-02d9-b3b1-0c5a9a68df89@vivier.eu> (raw)
In-Reply-To: <CAL1e-=ghxDLcU3iqkZ8q_sbk_DyR70t2a-jFtoNDVa7iTkMXsQ@mail.gmail.com>

Le 30/01/2020 à 12:09, Aleksandar Markovic a écrit :
> 14:34 Čet, 23.01.2020. Aleksandar Markovic <aleksandar.m.mail@gmail.com
> <mailto:aleksandar.m.mail@gmail.com>> је написао/ла:
>>
>> Extend support for ioctls in QEMU linux-user mode
>>
>>
>> PLANNED ACTIVITIES
>>
>> BACKGROUND
>>
>> There is currently 2500+ ioctls defined in Linux kernel. QEMU
> linux-user currently supports only several hundred. There is a constant
> need for expanding ioctl support in QEMU. Users use Linux-user mode in
> variety of setups (for example, building and testing tools and
> applications under chroot environment), and, on a regular basis, efforts
> by multiple people are made to fill in missing support. However, these
> efforts have been usually done on a piece-by-piece basis, i a limited
> way covering a partucular need. This project will take more proactive
> stance, and try to improve QEMU before users start complaining.
>>
>> PART I:
>>
>>    a) Add strace support for outputing ioctl IDs (the second argument
> of ioctl()) as strings rather than numbers - for all platform
> independant ioctls.
>>    b) Add strace support for printing the third argument of ioctl()
> (be it int, string, structure or array) - limited to selected ioctls
> that are frequently used.
>>
>> PART II:
>>
>>    a) Amend support for existing groups of ioctls that are not
> completed 100% (let's say, filesystem ioctls)
>>    b) Add support for a selected group of ioctls that are not
> currently supported (for example, dm ioctls, Bluetooth ioctls, or Radeon
> DRM ioctls)
>>
>> PART III:
>>
>>   a) Develop unit tests for selected ioctls that are already supported
> in QEMU.
>>
>> DELIVERABLES
>>
>> The deliverables are in the form of source code for each part,
> intended to be upstreamed, and time needed for upstreaming (addressing
> reviews, etc.) process is included int this project.
>>
>> The delivery of results can and should be distributed over larger
> period of time 2-3 months.
>>
>>
>> Montor: open (I propose Laurent Vivier)
>>
>> Student: open
> 
> Hello, Peter, Laurent, Stefan.
> 
> I presented in this thread two variants of a potential
> linux-user-related project for GSoC/Outreachy. The first variant is more
> focused on a particular area (ioctl support), while the second one
> covers wider set of current issues within linux-user. The pros and cons
> of both should be carefully assesed. I will leave to Peter and Laurent
> the final judgement if we want to go or not with this project and also
> the final formulation of the project.

I think the second variant (that includes new syscalls) is more
interesting for us and for the student.

> Stefan, there was an idea in this thread that this project contributes
> (apart to QEMU) to another ooen source project (LTP). In my layman view,
> this is an advantage. But, how does that fit into GSoC/Outreachy rules?
> 
> Laurent, all this seems to be dependant on whether you are ready to
> mentor the project. Are you?

Yes, of course.

> The deadline for submitting GSoC/Outreachy projects (within QEMU) is
> just around the corner (Feb 1). I leave to Laurent or Peter (should they
> give "go" to this proposal) to officially submit the project on our wiki
> page created for that purpose, in the form they deem the best.

Peter, is it ok for you?

Thanks,
Laurent



  reply	other threads:[~2020-01-30 11:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 13:34 [GSoC/Outreachy QEMU proposal] Extend support for ioctls in QEMU linux-user mode Aleksandar Markovic
2020-01-27  9:30 ` Stefan Hajnoczi
2020-01-27 16:30   ` Aleksandar Markovic
2020-01-28 14:28     ` Laurent Vivier
2020-01-28 17:32       ` Aleksandar Markovic
2020-01-28 17:37         ` Laurent Vivier
2020-01-28 14:32 ` Peter Maydell
2020-01-28 17:51   ` Aleksandar Markovic
2020-01-28 18:00     ` Peter Maydell
2020-01-28 20:48       ` Aleksandar Markovic
2020-02-05 11:16         ` Stefan Hajnoczi
2020-02-05 13:44           ` Laurent Vivier
2020-01-30 11:09 ` Aleksandar Markovic
2020-01-30 11:20   ` Laurent Vivier [this message]
2020-01-30 11:52     ` Peter Maydell
2020-01-31  8:37       ` Laurent Vivier
2020-02-05 10:45         ` Stefan Hajnoczi
2020-01-31 11:28   ` Stefan Hajnoczi

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=3d768689-b69f-02d9-b3b1-0c5a9a68df89@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).