All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Riku Voipio <riku.voipio@iki.fi>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4.
Date: Mon, 11 Jan 2016 14:54:35 +0100	[thread overview]
Message-ID: <5693B41B.1040907@vivier.eu> (raw)
In-Reply-To: <f7da4bfd-6baf-4133-9bbe-3514d52d8c63@iki.fi>



Le 11/01/2016 14:46, Riku Voipio a écrit :
> Hi,
> 
> On torstaina 24. joulukuuta 2015 21.04.38 EET, John Paul Adrian Glaubitz
> wrote:
>> Here are, as discussed previously, my proposed patches which change the
>> following:
>>
>> PATCH 1/2 updates the syscall table for m68k to match Linux 4.4. This
>> one should be very obvious.
>>
>> PATCH 2/2 adds the definitions for the socket calls SOCKOP_sendmmsg and
>> SOCKOP_recvmmsg and wires them up with the rest of the code. The
>> necessary function do_sendrecvmmsg() is already present in
>> linux-user/syscall.c. After adding these two definitions and wiring them
>> up, I no longer receive an error message about the unimplemented socket
>> calls when running "apt-get update" on Debian unstable running on qemu
>> with glibc_2.21 on m68k.
> 
> I've applied these changing the commit messages using the text above.
> However, a static busybox from debian/unstable doesn't work for me. With
> or without these patches I just get a target segfault.
> 
> Since debian-m68k list is talking about using qemu for builds, I take
> I'm missing something obvious here.

Not obvious. Adrian is working with my m68k branch of qemu (qemu-m68k).
Pure qemu supports only coldfire, if you want to test it, you can't use
debian. There is a coldfire image at http://wiki.qemu.org/Testing, but
of course, it doesn't use the syscalls added by these patches.

I'm currently working to be able to merge my m68k branch into mainstream
qemu. A first series of patch will be available in the few coming days.

Laurent

  reply	other threads:[~2016-01-11 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 18:59 [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 18:59 ` [Qemu-devel] [PATCH 2/2] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up John Paul Adrian Glaubitz
2015-12-24 21:16   ` Laurent Vivier
2015-12-24 19:04 ` [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 21:21   ` Laurent Vivier
2015-12-25  0:02     ` John Paul Adrian Glaubitz
2016-01-11 13:46   ` Riku Voipio
2016-01-11 13:54     ` Laurent Vivier [this message]
2016-01-11 13:57       ` John Paul Adrian Glaubitz
2016-01-11 14:10       ` Riku Voipio
2016-01-11 14:13         ` John Paul Adrian Glaubitz
2015-12-24 21:14 ` Laurent Vivier

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=5693B41B.1040907@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.