All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Petar Jovanovic <Petar.Jovanovic@imgtec.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"riku.voipio@linaro.org" <riku.voipio@linaro.org>,
	Petar Jovanovic <petar.jovanovic@rt-rk.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"afaerber@suse.de" <afaerber@suse.de>,
	"aurelien@aurel32.net" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v3 1/2] linux-user: create target_structsheader to place ipc_perm and shmid_dss
Date: Tue, 05 Nov 2013 14:46:52 +0000	[thread overview]
Message-ID: <p1li129a8z.fsf@linaro.org> (raw)
In-Reply-To: <56EA75BA695AE044ACFB41322F6D2BF44CCAB923@BADAG02.ba.imgtec.org>


Petar.Jovanovic@imgtec.com writes:

> ________________________________________
> From: Alex Bennée [alex.bennee@linaro.org]
<snip>
>
>> There is an awful lot of similarity between a lot of the structures
>> while not being totally identical. Given the syscall munging is common
>> is there not an argument for having a common header for this case?
>
> Hi Alex,
>
> I am not sure I understand your point. This used to be all in one file, now
> it is divided in arch-specific files that can be later populated with other
> target specific struct definitions. This was also suggested in the first
> review a month ago.

I've looked back and I can see the point of moving it out of the
syscall.c into the appropriate linux-user/${foo}/target_structs.h.
However for the cases where the given structure is identical maybe
linux-user/${foo}/target_structs.h should do an:

#include <linux-user/common/ipc_struct.h>

Having essentially the same definition in multiple places makes common
fixes potentially miss architectures. If a given architecture then needs
it's own special snowflake version it can of course not include the
common version and define it directly in target_structs.h.

Where is the reference for each of these structures? The kernels own
headers or glibc's for the appropriate arch?

-- 
Alex Bennée

  parent reply	other threads:[~2013-11-05 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 13:46 [Qemu-devel] [PATCH v3 1/2] linux-user: create target_structs header to place ipc_perm and shmid_ds Petar Jovanovic
2013-10-30 13:46 ` [Qemu-devel] [PATCH v3 2/2] linux-user: pass correct parameter to do_shmctl() Petar Jovanovic
2013-11-04 16:46 ` [Qemu-devel] [PATCH v3 1/2] linux-user: create target_structsheader to place ipc_perm and shmid_dss Alex Bennée
2013-11-04 18:55   ` Petar Jovanovic
2013-11-04 19:11     ` Peter Maydell
2013-11-05 14:46     ` Alex Bennée [this message]
2013-11-05 14:57       ` Peter Maydell
2013-11-06 20:04       ` Petar Jovanovic
2013-11-12 15:40         ` Petar Jovanovic
2013-11-19 23:03           ` Petar Jovanovic

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=p1li129a8z.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Petar.Jovanovic@imgtec.com \
    --cc=afaerber@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=petar.jovanovic@rt-rk.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@linaro.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 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.