From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <atish.patra@wdc.com>, Anup Patel <anup.patel@wdc.com>
Cc: linux-kernel@vger.kernel.org, Alan Kao <alankao@andestech.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
devicetree@vger.kernel.org, Enrico Weigelt <info@metux.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
linux-riscv@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v4 2/4] RISC-V: Add riscv_isa reprensenting ISA features common across CPUs
Date: Tue, 6 Aug 2019 14:54:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908061452570.13971@viisi.sifive.com> (raw)
In-Reply-To: <20190803042723.7163-3-atish.patra@wdc.com>
Hi Anup, Atish,
On Fri, 2 Aug 2019, Atish Patra wrote:
> From: Anup Patel <anup.patel@wdc.com>
>
> This patch adds riscv_isa integer to represent ISA features common
> across all CPUs. The riscv_isa is not same as elf_hwcap because
> elf_hwcap will only have ISA features relevant for user-space apps
> whereas riscv_isa will have ISA features relevant to both kernel
> and user-space apps.
>
> One of the use case is KVM hypervisor where riscv_isa will be used
> to do following operations:
>
> 1. Check whether hypervisor extension is available
> 2. Find ISA features that need to be virtualized (e.g. floating
> point support, vector extension, etc.)
>
> Signed-off-by: Anup Patel <anup.patel@wdc.com>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
Do you have any opinions on how this patch might change for the Z-prefix
extensions? This bitfield approach probably won't scale, and with the
EXPORT_SYMBOL(), it might be worth trying to put together a approach that
would work over the long term?
- Paul
next prev parent reply other threads:[~2019-08-06 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 4:27 [PATCH v4 0/4] Miscellaneous fixes Atish Patra
2019-08-03 4:27 ` [PATCH v4 1/4] RISC-V: Remove per cpu clocksource Atish Patra
2019-08-06 21:37 ` Paul Walmsley
2019-08-07 8:04 ` Daniel Lezcano
2019-08-03 4:27 ` [PATCH v4 2/4] RISC-V: Add riscv_isa reprensenting ISA features common across CPUs Atish Patra
2019-08-06 21:54 ` Paul Walmsley [this message]
2019-08-07 4:12 ` Anup Patel
2019-08-07 6:51 ` Christoph Hellwig
2019-08-07 6:55 ` Anup Patel
2019-08-03 4:27 ` [PATCH v4 3/4] RISC-V: Fix unsupported isa string info Atish Patra
2019-08-03 4:27 ` [PATCH v4 4/4] dt-bindings: Update the riscv,isa string description Atish Patra
2019-08-06 21:43 ` Paul Walmsley
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=alpine.DEB.2.21.9999.1908061452570.13971@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=alankao@andestech.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@sifive.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).