From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH v2 2/3] RISC-V: Use Linux logical cpu number instead of hartid
Date: Wed, 5 Sep 2018 12:03:51 -0700 [thread overview]
Message-ID: <20180905190351.GB1420@infradead.org> (raw)
In-Reply-To: <d79833a8-98ae-fa19-9a7c-0afeb3d0bb92@wdc.com>
On Tue, Sep 04, 2018 at 02:43:13PM -0700, Atish Patra wrote:
> On 9/4/18 2:36 PM, Christoph Hellwig wrote:
> > On Tue, Sep 04, 2018 at 01:35:10PM -0700, Atish Patra wrote:
> > > sure. How about this ?
> >
> > That would work, but why not just keep calling sbi_remove_sfence_vma
> > directly from flush_tlb_all?
> >
> I guess that's fine too. I just wanted to keep all flush_tlb_* same format
> to make it more coherent.
I'd just keep it simple by calling directly. While the compiler would
probably optimize away the branch in an inline function we can just
avoid it entirely that way.
next prev parent reply other threads:[~2018-09-05 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535445370-19004-1-git-send-email-atish.patra@wdc.com>
2018-08-30 13:53 ` [PATCH v2 0/3] RISC-V: Add new smp features Anup Patel
2018-08-30 14:11 ` Christoph Hellwig
2018-08-30 14:15 ` Anup Patel
2018-08-30 14:18 ` Anup Patel
2018-08-30 16:04 ` Atish Patra
[not found] ` <1535445370-19004-2-git-send-email-atish.patra@wdc.com>
2018-08-31 6:03 ` [PATCH v2 1/3] RISC-V: Add logical CPU indexing for RISC-V Christoph Hellwig
2018-09-04 17:59 ` Atish Patra
[not found] ` <1535445370-19004-3-git-send-email-atish.patra@wdc.com>
2018-08-31 6:11 ` [PATCH v2 2/3] RISC-V: Use Linux logical cpu number instead of hartid Christoph Hellwig
2018-09-04 20:35 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:43 ` Atish Patra
2018-09-05 19:03 ` Christoph Hellwig [this message]
[not found] ` <1535445370-19004-4-git-send-email-atish.patra@wdc.com>
2018-08-31 6:18 ` [PATCH v2 3/3] RISC-V: Support cpu hotplug Christoph Hellwig
2018-09-04 18:08 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:40 ` Atish Patra
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=20180905190351.GB1420@infradead.org \
--to=hch@infradead.org \
--cc=linux-riscv@lists.infradead.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 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).