From: Chen Gang <gang.chen.5i5j@gmail.com>
To: "jejb@parisc-linux.org" <jejb@parisc-linux.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures
Date: Sat, 06 Dec 2014 23:57:21 +0800 [thread overview]
Message-ID: <54832761.1050700@gmail.com> (raw)
In-Reply-To: <54822B19.2070804@gmail.com>
Hello Maintainers:
After this patch, our parisc can pass allmodconfig in linux next tree,
for me, we can say parisc specific code have no touch for allmodconfig.
:-)
But for parisc gcc latest upstream compiler, I found several issues, and
I shall try to analyse them and communicate with gcc related members.
And I also want to consult about parisc assembly instructions, I can not
find the related reference documents, could you help to have a check (or
provide some related information for it)? related contents are below:
parisc support several store instructions: 'stb' (for store byte),
'stw(m)' (for store word), and 'std' (for store double word).
They should be in the same format in binary code, and have neighbour
numbers, and 'stw(m)' need be in the middle of 'stb' and 'std'. one
sample for the instruction 'inst' (it is 'unsigned int'):
- for ((inst >> 26) != 0x3):
stb: 0x18, or 0x19,
stw: 0x1a, stwm: 0x1b,
std: 0x1c.
- else ((inst >> 26) == 0x3), need check '(inst >> 6) & 0xf':
stb: 0x08, or 0x09,
stw: 0x0a,
std: 0x0b.
it is about my binutils/gdb patch for parisc, gdb want to recognize
'st??' to find the position for saving relate context (registers).
Welcome any suggestions, ideas, and completions.
Thanks.
On 12/06/2014 06:00 AM, Chen Gang wrote:
> On 12/05/2014 02:54 PM, Minchan Kim wrote:
>> On Fri, Dec 05, 2014 at 06:58:29AM +0800, Chen Gang wrote:
>>> For uapi, need try to let all macros have same value, and MADV_FREE is
>>> added into main branch recently, so need redefine MADV_FREE for it.
>>>
>>> At present, '8' can be shared with all architectures, so redefine it to
>>> '8'.
>>>
>>> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
>>
>>
>> Hello Chen,
>>
>> Thanks for looking at this.
>> Feel free to add my sign.
>>
>> Acked-by: Minchan Kim <minchan@kernel.org>
>>
>
> OK, thanks.
>
> Originally I sent the same patch like you sent (but later than yours).
> Geert suggested to use same value for MADV_FREE, and Carlos confirmed
> it and suggested more things (sorry, I forgot to Cc them in this mail).
>
>
> Thanks.
>
--
Chen Gang
Open share and attitude like air water and life which God blessed
next prev parent reply other threads:[~2014-12-06 15:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 22:58 [PATCH] arch: uapi: asm: mman.h: Let MADV_FREE have same value for all architectures Chen Gang
2014-12-04 22:58 ` Chen Gang
2014-12-05 0:14 ` Darrick J. Wong
[not found] ` <20141205001446.GC10064-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2014-12-05 21:51 ` Chen Gang
2014-12-05 21:51 ` Chen Gang
2014-12-05 6:54 ` Minchan Kim
2014-12-05 22:00 ` Chen Gang
2014-12-06 15:57 ` Chen Gang [this message]
2014-12-07 16:14 ` John David Anglin
2014-12-07 22:35 ` Chen Gang
2014-12-24 15:27 ` Chen Gang
[not found] ` <54822B19.2070804-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-12-10 1:45 ` Chen Gang
2014-12-10 1:45 ` Chen Gang
[not found] ` <5480E715.3020900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-12-09 14:46 ` Fwd: " Chen Gang
[not found] ` <54870B36.3000901-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-12-09 14:51 ` Fwd: " Chen Gang
2015-10-28 7:18 ` Minchan Kim
2015-10-28 7:18 ` Minchan Kim
[not found] ` <56308B0B.3000801@hotmail.com>
2015-10-28 8:45 ` Chen Gang
2015-10-28 8:45 ` Chen Gang
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=54832761.1050700@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=brobecker@adacore.com \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.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 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.