All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Alan Kao <alankao@andestech.com>,
	Dmitriy Cherkasov <dmitriy@oss-tech.org>,
	Andreas Schwab <schwab@suse.de>,
	Palmer Dabbelt <palmer@sifive.com>,
	Johan Hovold <johan@kernel.org>,
	linux-kernel@vger.kernel.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Anup Patel <anup@brainfault.org>,
	linux-riscv@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.
Date: Mon, 25 Feb 2019 09:34:39 +0100	[thread overview]
Message-ID: <20190225083439.GA4747@localhost> (raw)
In-Reply-To: <1550864500-13652-7-git-send-email-atish.patra@wdc.com>

On Fri, Feb 22, 2019 at 11:41:40AM -0800, Atish Patra wrote:
> Currently, we set hwcap based on first valid hart from DT. This may not
> be correct always as that hart might not be current booting cpu or may
> have a different capability.
> 
> Set hwcap as the capabilities supported by all possible harts with "okay"
> status.
> 
> Signed-off-by: Atish Patra <atish.patra@wdc.com>

Reviewed-by: Johan Hovold <johan@kernel.org>

_______________________________________________
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: Johan Hovold <johan@kernel.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-riscv@lists.infradead.org, Alan Kao <alankao@andestech.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Andreas Schwab <schwab@suse.de>, Anup Patel <anup@brainfault.org>,
	Dmitriy Cherkasov <dmitriy@oss-tech.org>,
	Johan Hovold <johan@kernel.org>,
	linux-kernel@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities.
Date: Mon, 25 Feb 2019 09:34:39 +0100	[thread overview]
Message-ID: <20190225083439.GA4747@localhost> (raw)
In-Reply-To: <1550864500-13652-7-git-send-email-atish.patra@wdc.com>

On Fri, Feb 22, 2019 at 11:41:40AM -0800, Atish Patra wrote:
> Currently, we set hwcap based on first valid hart from DT. This may not
> be correct always as that hart might not be current booting cpu or may
> have a different capability.
> 
> Set hwcap as the capabilities supported by all possible harts with "okay"
> status.
> 
> Signed-off-by: Atish Patra <atish.patra@wdc.com>

Reviewed-by: Johan Hovold <johan@kernel.org>

  parent reply	other threads:[~2019-02-25  8:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 19:41 [v6 PATCH 0/6] Various SMP related fixes Atish Patra
2019-02-22 19:41 ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 1/6] RISC-V: Do not wait indefinitely in __cpu_up Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 2/6] RISC-V: Move cpuid to hartid mapping to SMP Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 3/6] RISC-V: Remove NR_CPUs check during hartid search from DT Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 4/6] RISC-V: Allow hartid-to-cpuid function to fail Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 5/6] RISC-V: Compare cpuid with NR_CPUS before mapping Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-22 19:41 ` [v6 PATCH 6/6] RISC-V: Assign hwcap as per comman capabilities Atish Patra
2019-02-22 19:41   ` Atish Patra
2019-02-25  3:35   ` Anup Patel
2019-02-25  3:35     ` Anup Patel
2019-02-25  8:34   ` Johan Hovold [this message]
2019-02-25  8:34     ` Johan Hovold
2019-03-04  8:36   ` Andreas Schwab
2019-03-04  8:36     ` Andreas Schwab
2019-03-04 19:06 ` [v6 PATCH 0/6] Various SMP related fixes Palmer Dabbelt
2019-03-04 19:06   ` Palmer Dabbelt

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=20190225083439.GA4747@localhost \
    --to=johan@kernel.org \
    --cc=alankao@andestech.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=dmitriy@oss-tech.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@suse.de \
    --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 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.