From: Atish Patra <atish.patra@wdc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "palmer@sifive.com" <palmer@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"anup@brainfault.org" <anup@brainfault.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"damein@vger.kernel.org" <damein@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] RISC-V: Use Linux logical cpu number instead of hartid
Date: Tue, 4 Sep 2018 14:43:13 -0700 [thread overview]
Message-ID: <d79833a8-98ae-fa19-9a7c-0afeb3d0bb92@wdc.com> (raw)
In-Reply-To: <20180904213654.GB2078@infradead.org>
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.
Regards,
Atish
next prev parent reply other threads:[~2018-09-04 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 8:36 [PATCH v2 0/3] RISC-V: Add new smp features Atish Patra
2018-08-28 8:36 ` [PATCH v2 1/3] RISC-V: Add logical CPU indexing for RISC-V Atish Patra
2018-08-31 6:03 ` Christoph Hellwig
2018-09-04 17:59 ` Atish Patra
2018-08-28 8:36 ` [PATCH v2 2/3] RISC-V: Use Linux logical cpu number instead of hartid Atish Patra
2018-08-31 6:11 ` Christoph Hellwig
2018-09-04 20:35 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:43 ` Atish Patra [this message]
2018-09-05 19:03 ` Christoph Hellwig
2018-08-28 8:36 ` [PATCH v2 3/3] RISC-V: Support cpu hotplug Atish Patra
2018-08-31 6:18 ` Christoph Hellwig
2018-09-04 18:08 ` Atish Patra
2018-09-04 21:36 ` Christoph Hellwig
2018-09-04 21:40 ` Atish Patra
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
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=d79833a8-98ae-fa19-9a7c-0afeb3d0bb92@wdc.com \
--to=atish.patra@wdc.com \
--cc=anup@brainfault.org \
--cc=damein@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®