From: Christoph Hellwig <hch@infradead.org>
To: Alan Kao <alankao@andestech.com>
Cc: Palmer Dabbelt <palmer@sifive.com>,
Anup Patel <Anup.Patel@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <Atish.Patra@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2] RISC-V: Always compile mm/init.c with cmodel=medany
Date: Sun, 24 Mar 2019 23:48:26 -0700 [thread overview]
Message-ID: <20190325064826.GA29111@infradead.org> (raw)
In-Reply-To: <20190325052550.GA30996@andestech.com>
On Mon, Mar 25, 2019 at 01:25:50PM +0800, Alan Kao wrote:
> Hi Anup,
>
> Sorry for being late to the party. I think one more thing should
> move together with setup_vm():
Ah, I wonded about that yesterday but wasn't sure. Maybe notrace
is a little cleaner? Either way we should probably document both
the mcmodel and notrace assumptions in source comments for the next
person touching this code.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Alan Kao <alankao@andestech.com>
Cc: Anup Patel <Anup.Patel@wdc.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <Atish.Patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2] RISC-V: Always compile mm/init.c with cmodel=medany
Date: Sun, 24 Mar 2019 23:48:26 -0700 [thread overview]
Message-ID: <20190325064826.GA29111@infradead.org> (raw)
In-Reply-To: <20190325052550.GA30996@andestech.com>
On Mon, Mar 25, 2019 at 01:25:50PM +0800, Alan Kao wrote:
> Hi Anup,
>
> Sorry for being late to the party. I think one more thing should
> move together with setup_vm():
Ah, I wonded about that yesterday but wasn't sure. Maybe notrace
is a little cleaner? Either way we should probably document both
the mcmodel and notrace assumptions in source comments for the next
person touching this code.
next prev parent reply other threads:[~2019-03-25 6:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 3:37 [PATCH v2] RISC-V: Always compile mm/init.c with cmodel=medany Anup Patel
2019-03-25 3:37 ` Anup Patel
2019-03-25 5:25 ` Alan Kao
2019-03-25 5:25 ` Alan Kao
2019-03-25 6:48 ` Christoph Hellwig [this message]
2019-03-25 6:48 ` Christoph Hellwig
2019-03-25 7:01 ` Anup Patel
2019-03-25 7:01 ` Anup Patel
2019-03-26 2:22 ` Palmer Dabbelt
2019-03-26 2:22 ` Palmer Dabbelt
2019-03-26 4:01 ` Anup Patel
2019-03-26 4:01 ` Anup Patel
2019-03-27 0:10 ` Alistair Francis
2019-03-27 0:10 ` Alistair Francis
2019-03-25 6:59 ` Anup Patel
2019-03-25 6:59 ` Anup Patel
2019-03-25 6:12 ` Mike Rapoport
2019-03-25 6:12 ` Mike Rapoport
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=20190325064826.GA29111@infradead.org \
--to=hch@infradead.org \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=alankao@andestech.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@linux.ibm.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 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.